Releases are mutations that propagates to an environment. In this Section, you will learn how to perform and monitor a release that makes a change to the environment.
Facets is built on a key principle that any changes (release) to an environment has to happen through a single mechanism. These changes could be of
- New code or updates (new builds)
- New resources or updates
- New interactions, schema, policies or updates
Releases are of two types
Scheduled Release: A Scheduled release pattern is defined in the "edit" environment section in the "Misc" tab. For e.g., a
30 5 * * *would mean a scheduled release (full) will happen at
5:30 AM, every day.
On-demand Release: An on-demand release can be performed in an environment from the "Releases" page. You can make a full or partial release from this page.
- Release - Perform a full release i.e. every resource on the Blueprint and their qualified builds will sync to the environment
- Selective - Perform a selective release of one or selected resources. This is usually used as a hotfix to the environment
Once a release is performed the following details are available for it.
|When was the release triggered
|SUCCESS or FAIL
|The git commit up to which the IDP has pulled the changes
|RELEASE (Indicates a full release)
LAUNCH (Environment launch)
HOTFIX (Indicates a selective release)
|Either a user
Facets Bot (indicating a scheduled release)
|1. Release Details
2. Terraform Logs
The release details Action shows the resource changes i.e Creations, Modification (i.e. new versions of apps) or Destruction.
The release logs provide a detail view of the generated terraform logs.
The release summary page is aggregated release summary for last 30 days. This provides metrics that can lead to improvement in the SDLC.
|Number of Successful Releases in last 30 days
|Number of Failed Releases in last 30 days
|Average deployment per day
|Change Failure Rate
|Percentage of changes that resulted in a failure
Updated 3 months ago