Create a default static Environment
Create and pin a long-lived dev-0 Environment with supported Lifecycle controls.
A static Environment does not use the usual pull-request teardown lifecycle.
Teams use dev-0 as a fallback for Services that an ephemeral Environment does
not override.
Prerequisites
Required items are the Lifecycle CLI, Environment management permission, and an onboarded repository with the fallback Services.
Lifecycle can reserve dev-0 with an empty placeholder. Release the name with
the CLI procedure below.
Create dev-0
Examine the placeholder
If this is the empty reserved placeholder, continue. If it is a non-placeholder Environment, do not replace it.
Release the reserved name
If your installed CLI or server rejects this operation, stop and contact the platform operator. The operator can upgrade Lifecycle or give you the supported migration procedure.
Create the source Environment
Create a long-lived pull request in the onboarded repository. Its
lifecycle.yaml must select the fallback Services and their default
branches. Wait until the generated Environment is deployed.
Rename and pin it
--static prevents usual automatic teardown. When a default branch moves,
--track-defaults redeploys Services that have no explicit branch override.
Remove the placeholder
Check the fallback
Make sure that the output identifies the Environment as static. Check that default-branch tracking is enabled. Make sure that all fallback Services are Ready.
In a different ephemeral Environment, do not select an optional Service. Make sure that
its generated template variables point to the Service from dev-0. The fallback
comes from each Service’s configured defaultUUID. The template resolver does
not always use dev-0.
Change or remove the static Environment
To stop tracking default branches without removing the Environment:
To remove it, first unpin and then destroy it: