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.
| Property | Type | Description |
|---|---|---|
| apiVersion | string | API schema version. Must be lowops.manifests.v1. |
| kind | string | Resource kind. Must be ReleaseTrack. |
| metadata | map | The engine reads the reserved keys name, organizational-unit, and organization to resolve the identity and the parents. |
| spec | Spec | Desired 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.
| Property | Type | Description |
|---|---|---|
| description | string | Optional description of the release track. It is documentation only. No cloud resource carries it. |
| preReleaseStages | list of Stage | Ordered pre-release (integration) stages. They run on pull requests before you create a release, usually in non-production or ephemeral preview environments. |
| releaseStages | list of Stage | Ordered stages for the standard release. They run when you tag a new version, usually to promote the artifact through staging to production. |
| hotfixStages | list of Stage | Ordered 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.
| Property | Type | Description |
|---|---|---|
| environments | list of string | Names of the Environment manifests in this stage. The application must deploy to every one before promotion to the next stage. |
| approvalPolicy | ApprovalPolicy | Approval 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.
| Property | Type | Description |
|---|---|---|
| stakeholder | Stakeholder | Leaf policy. It passes when the named stakeholder (a user or group) approves. |
| anyOf | ApprovalSet | Any-of (OR) composite. It passes when at least one nested policy passes. |
| allOf | ApprovalSet | All-of (AND) composite. It passes when every nested policy passes. |
| quorum | ApprovalSet | Quorum 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.
| Property | Type | Description |
|---|---|---|
| policies | list of ApprovalPolicy | Child policies that the parent operator combines. |
| minApprovals | int32 | Minimum 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.
| Property | Type | Description |
|---|---|---|
| userEmail | string | Email address of an OrganizationUser. |
| groupEmail | string | Email address of an OrganizationUserGroup. |