You can create a package retention policy (policy.PackageRetentionPolicy) that retains the deployment packages based on the configured regular expression. Deployed packages are never removed by the package retention policy. If a deployed package is part of the packages identified for removal, then it will be skipped, with no impact on other packages.
We recommended that you regularly create a backup of your Deploy server.
Using the Deploy Compare feature, you can compare two or more configuration item (CI) trees. In addition to comparing the chosen configuration items, it recursively traverses the CI tree and compares each CI from one tree with matching configuration items from other trees.
Deploy uses a database to store all data such as configuration items (CIs), deployment packages, logging, etc. Deploy can use the filesystem or a database for binary artifacts (deployment packages) and CIs and CI history.
Use the Deploy Explorer to view and manage the configuration items (CIs) in your repository, deploy and undeploy applications, connect to your infrastructures, and provision and deprovision environments.
The Deploy database is called the repository. It stores all configuration items (CIs), binary files - such as deployment packages, and Deploy security configuration - such as user accounts and rights. By default, Deploy uses an internal database that stores data on the file system. This configuration is intended for temporary use and is not recommended for production use. In production environments, the repository is stored in a relational database on a external database server. For more information, see using a database.
Export a deployment package (DAR file) using the Deploy GUI
The repository object in the Deploy command-line interface (CLI) allows you to export the Deploy repository tree to a ZIP file that can be imported into the same Deploy server or into another Deploy server. The ZIP file contains all configuration item (CI) properties, including artifact files.
A blueprint repository is a remote repository that contains templates and source code for blueprint functionality. Each time you run the XL CLI xl blueprint command, it fetches files from the blueprint repository.
A Stitch repository is a source of rules and macros YAML files, and their associated content. A repository can be any Git repository or a local folder that contains a valid Stitch YAML file. When a Stitch source is added to the configuration, Deploy scans the whole repository or the folder structure recursively, drilling down the folder structure attempting to find valid definitions of Stitch YAML rules. It will look for files with the stitch-rules prefix, and a yaml or yml suffix (e.g. stitch-rules.yaml or stitch-rules-k8s-labels.yaml).
To support secure communications, Deploy can generate a self-signed digital certificate. This can cause issues in situations where Deploy needs to be accessed using a URL other than https4516, because the Common Name in the certificate is localhost.