📄️ Work With the YAML Format for Deploy
This topic provides information about how to work with the YAML format for Deploy.
📄️ YAML Snippets Reference in Deploy
<!---
📄️ Manage Values in YAML
You can manage values separately from your DevOps as Code YAML files so that they can be pulled in when applying XL YAML files. DevOps as Code supports multiple methods to configure and manage values including a dedicated file format using the .xlvals extension, environment variables or by explicitly specifying a value in XL CLI command syntax.
📄️ Manage Deploy Permissions in YAML
You can specify and maintain global permissions, roles, and users for Deploy in YAML, enabling you to manage this aspect of your Deploy configuration "as code".
📄️ Source Control Management in YAML
DevOps as Code allows you to send source control information from the git repository in which a YAML template is maintained. This can be viewed in the Deploy or Release GUI, and helps to establish the relationship between the YAML files and your Release and Deploy instances, providing visibility into the specific file and commit from which a change was made.
📄️ Track Progress Using XL CLI Output
You can follow deployment and release pipeline activities defined in your YAML files as they are executed by Deploy or Release using the output provided in the XL Command Line Interface (CLI).
📄️ Composable Blueprints
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.