This topic provides a reference for the DevOps as Code YAML file structure for a blueprint. You can review the publicly-available blueprint files alongside the content in this topic to get a better understanding of how fields, values and options are specified.
DevOps as Code provides developers and other technical users with an alternative way to interact with the Digital.ai release orchestration and deployment automation products using text-based specifications to define application artifacts, resource specifications and releases and a simple command line interface to execute them.
From Digital.ai Release 10.2, you can use GitOps-enabled version control to store and track changes to folder entities in the form of YAML files (Releasefile.yaml) within a Git repository.
Release calculates a risk level for each release based on different factors such as flags, failed or failing states, or due dates. While the Release GUI enables you to manage risk profile setting and thresholds, you can also choose to manage your risk profiles for your releases using YAML specifications.
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.
This topic provides information about how to work with the YAML format for Deploy.
This topic provides information about how to work with the YAML format for Release.
This topic includes some useful snippets to get started when writing DevOps as Code YAML files that can be applied to Deploy.
<!---