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.
* Deploy 23.1 and later lets you cache frequently accessed data for better performance and reduced latency.
This section describes how to install Central Configuration service as a separate service when you install or upgrade the Digital.ai Deploy solution.
This topic describes the transition to a Kubernetes-based containerized Deploy solution, where Digital.ai Deploy shared configuration files are moved to a centralized location managed by the Central Configuration Management server.
During our performance testing activity, we used the 'Cache hit %' metric to understand how caching improves performance. This metric indicates the percentage of overall data requests that were successfully retrieved from the cache.
Note: Any failure during the caching setup will be captured in the logs but will not stop the application from starting.
Note: Active-Hot-standby mode is not supported for caching setup.
You can retrieve and delete cached data using the following actuator API endpoints:
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.
This topic provides information on JSON Patch, a format for describing changes to a JSON document. JSON Patch can be used to avoid sending the entire 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.
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.
<!---
<!---