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.
* When you install Digital.ai Deploy, the Central Configuration feature is implemented by default on the application server (Master) as an embedded service.
As we move towards Kubernetes-based containerized Deploy solution, the Digital.ai Deploy shared configuration files are moved to a centralized location from where they are managed by the Central Configuration Management server. The idea of Central Configuration is to have one central place—in this case, the Digital.ai Deploy's Master server—where you can store, distribute, and manage configuration data for master/worker pods in your cluster. Digitial.ai Central Configuration is the process of maintaining and managing the configuration from a centralized location in the file system. With a centralized management, you can configure workers and masters easily and more efficiently. For example, if you have a Master-Master and Master-Worker setup with two masters and two workers, before Central Configuration you had to individually modify the configuration on all four instances. With the Central Configuration, the configurations are automatically reflected in all the instances.
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.
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.
Stitch macros are reusable building blocks which group the common processors used inside of Stitch rules.
JSON Patch is a format for describing changes to a JSON document. It can be used to avoid sending a whole document when only a part has changed.
This topic provides an overview of the patch dictionary feature and an example scenario that shows how you can use patch dictionaries to manage the substitution of configuration values during application deployment.
DevOps as Code uses a declarative YAML format to construct specifications that can be executed by Deploy and Release using the XL CLI. This topic provides a reference for the DevOps as Code YAML file structure for each available kind for Deploy. It also includes information on using the Spec section of the YAML file which provides the details of the configuration.
DevOps as Code uses a declarative YAML format to construct specifications that can be executed by Deploy and Release using the XL CLI. This topic provides a reference for the DevOps as Code YAML file structure for each available kind for Release. It also includes information on using the Spec section of the YAML file which provides the details of the configuration.
<!---
<!---