Skip to main content

Release Track

ReleaseTrack​

Promotion lifecycle ("Path to Production") for a group of applications.

It defines the ordered stages, target environments, and approvals that promote artifacts from pre-release validation to production, plus a hotfix path. It provisions no GCP resource. The stages drive the CD pipeline, and its child ApplicationSet manifests reference them.

PropertyTypeDescription
apiVersionstringAPI schema version. Must be lowops.manifests.v1.
kindstringResource kind. Must be ReleaseTrack.
metadatamapThe engine reads the reserved keys name, organizational-unit, and organization to resolve the identity and the parents.
specSpecDesired release-track configuration. See Spec.

Spec​

User-provided release track configuration.

Three promotion pipelines: pre-release, release, and hotfix. Each is an ordered list of stages that the engine validates against the org tree and that child ApplicationSet manifests reference.

PropertyTypeDescription
descriptionstringOptional description of the release track. It is documentation only. No cloud resource carries it.
preReleaseStageslist of StageOrdered pre-release (integration) stages. They run on pull requests before you create a release, usually in non-production or ephemeral preview environments.
releaseStageslist of StageOrdered stages for the standard release. They run when you tag a new version, usually to promote the artifact through staging to production.
hotfixStageslist of StageOrdered stages of the accelerated path that ships urgent hotfixes to production with minimal lead time and keeps the governance of the track.

Stage​

Phase of a deployment strategy.

Lists the environments that deploy together before the release continues.

PropertyTypeDescription
environmentslist of stringNames of the Environment manifests in this stage. The application must deploy to every one before promotion to the next stage.
approvalPolicyApprovalPolicyApproval policy that must pass before the release leaves this stage. The engine checks that the referenced stakeholders exist.

ApprovalPolicy​

Recursive rule for who must approve a deployment stage.

A node is a leaf with one stakeholder, or an any-of, all-of, or quorum composite of nested policies.

PropertyTypeDescription
stakeholderStakeholderLeaf policy. It passes when the named stakeholder (a user or group) approves.
anyOfApprovalSetAny-of (OR) composite. It passes when at least one nested policy passes.
allOfApprovalSetAll-of (AND) composite. It passes when every nested policy passes.
quorumApprovalSetQuorum composite. It passes when at least min_approvals nested policies pass.

ApprovalSet​

Nested approval policies of a composite node.

For a quorum node, min_approvals sets how many children must pass.

PropertyTypeDescription
policieslist of ApprovalPolicyChild policies that the parent operator combines.
minApprovalsint32Minimum number of nested policies that must pass in a quorum composite. The any-of and all-of operators ignore it.

Stakeholder​

Approver identified by email address.

A stakeholder is a user or a group that exists in the organization.

PropertyTypeDescription
userEmailstringEmail address of an OrganizationUser.
groupEmailstringEmail address of an OrganizationUserGroup.