Environment variables

Sets one environment variable, creating it if absent. Names the platform sets on the serving container itself are rejected with 422, as they are on create. A write that changes the stored value records a new version carrying the live environment set and the same image. If that image is deployable, the write pins it as activeVersionId and rolls the workload when the app can take one (active, initializing, or failed which becomes initializing). A stopped or stopping app pins the version and rolls it on resume. A write that leaves the stored value unchanged records no version and does not roll. A write while a rollout of this app is still in flight, or to a failed app while the workers of its failed rollout are still stopping, returns 409 Conflict and does not store the value. Each changing write is serialised behind that rollout, so setting several variables one at a time is that many sequential rolls with 409s between them. Replace the whole set in one request with PATCH /v1/apps/{appId} environmentVariables. An app holds at most 100 environment bindings in total, plain variables plus attached secrets, the same combined ceiling AppCreate.environmentVariables declares (create rejects secrets in-request, attach grows the set later). Overwriting an existing variable is always allowed. Adding one past the ceiling returns 422. The name must not collide with a secret already attached to this app (the secret's injected env var name). Secrets and plain env vars share the pod environment. A duplicate would be resolved last-wins by kubelet with no error, so the server rejects it with 422. The reverse check applies on attach.

Removes one environment variable. A successful delete records a new version carrying the remaining environment set and the same image. If that image is deployable, the delete pins it as activeVersionId and rolls the workload when the app can take one (active, initializing, or failed which becomes initializing). A stopped or stopping app pins the version and rolls it on resume. A delete of a key that is present while a rollout of this app is still in flight, or while the workers of a failed app's failed rollout are still stopping, returns 409 Conflict and does not remove the value. A name that is not present returns 404 even during that window.