Do not run this script on production unless you know what you are doing.

Do not run this script when reindexation is occurring.

slapos_erp5: [Administration] Add script for updateRoleMapping only at the portal types that contains Roles.

This is script for SlapOS Master

The Owner is not assignee anymore, only the destination_section of the hosting subscription.

  Configure in a way that KVM can use be set with real IPv6 inside provided by slapos.

destination_section could not be set, so the role was never used.

/reviewed-on !52

  This allow during a subscription process, create a user and them create all
  documents using that user w/o rely on proxy roles (keeping good ownership
  across the documents).

  slapos_erp5: release new security with local_role_group_id
  slapos_cloud: include more security_uids columns
  slapos_cloud: set extra security_uids configuration.
  slapos_erp5: Remove duplicated entry on roles
  slapos_erp5: Assignee on [Software/Slave] Instance comes from the Hosting Subscription
  slapos_configurator: erp5_security_uid_innodb_catalog is installed now.
  slapos_erp5: Software Installation, Owner shoulnd't be the Assignee but the Requester.
  slapos_erp5: Update RoleSecurity Tests
  slapos_cloud: testSlapOSCloudWorkflow, New security requires Slave Instance be linked to a HS
  slapos_erp5: R-SHADOW-PERSON is only present on Payments w/o Destination Section

Expose buildout debugging capabilities in `slapos node software` and `slapos node instance` with a `--buildout-debug` command line option.

From buildout's command line reference:

> `-D`
>  Debug errors. If an error occurs, then the post-mortem debugger will be started. This is especially useful 
>  for debugging recipe problems.

This is to make it easier to debug instance profiles written as jinja templates.

This fix from buildout nexedi/slapos.buildout!17 is recommended, otherwise slapos node does not realize there was an error in buildout if that error is debugged.

/reviewed-on nexedi/slapos.core!51

This is helpfull when you need to include "as after installation" scripts, where things move foward with no questions asked.

Introduce a --buildout-debug option to slapos node software and slapos
node instance, that will run buildout with -D flag.

Add a `debug` argument, False by default, which if true keeps
interactive stdin and stdout.

slapos/grid/SlapObject.py: If there is .shared file in software directory, don't upload binary cache. It is the mark of shared software.

/reviewed-on nexedi/slapos.core!50

  This simplifies 2 pages on the tutorials.