5 docs tagged with "permissions"

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.

Step-by-step guide to configuring permissions for Argo CD integration with Digital.ai Release live deployments, including RBAC, service accounts, and best practices.

Connections are used to configure Release to integrate with third-party applications. Connections are integration credentials that store authentication information required for Release plugins to securely communicate with third-party applications.

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".

This topic describes how to create, run, and manage workflows.