3 docs tagged with "roles"

Multiple blueprints can be composed into one master blueprint which specifies the deployment model for multiple included blueprints, by using includeBefore and includeAfter parameters. This allows you to scale your deployment and release models with any number of blueprints. During the implementation of a composed blueprint, the CLI will work through the blueprints in the sequence defined, merging the questions into a single list and applying any custom values that were defined in the composed blueprint. For more information on the YAML fields that enable composable blueprints, see IncludeBefore/IncludeAfter fields for composability.

Release uses a role-based access control (RBAC) model. Teams can be defined on each folder, template, or release—for example, a Development team, a QA team, an OPS team, and a Release Management team—and permissions are assigned to those teams at the folder, template, and release levels. Permissions defined at the folder level are inherited by all templates and releases within it. Teams can also be configured directly on individual templates or releases that are not in a folder.

You can specify and maintain global permissions, roles, and users for Release in YAML, enabling you to manage this aspect of your Release configuration "as code".