Skip to content

Rename the init action variable out of the reserved namespace - #219

Merged
csandanov merged 1 commit into
masterfrom
codex/rename-init-action-env
Aug 22, 2026
Merged

Rename the init action variable out of the reserved namespace#219
csandanov merged 1 commit into
masterfrom
codex/rename-init-action-env

Conversation

@csandanov

Copy link
Copy Markdown
Member

Reads WODBY2_SERVICE_INIT_ACTION instead of WODBY_INIT_ACTION.

WODBY_* is reserved: ValidateUserEnvVarName rejects it, and a service manifest may only declare such a name when a Super Admin, Wodbot, or a full-access member of the wodby-2 organization publishes it. Importing one of those manifests into any other organization fails with "Environment variable name ... is reserved by Wodby", which made the init action unusable outside the Wodby orgs.

The reserved prefix is WODBY_ exactly, so WODBY2_ is outside it — the same escape the existing WODBY2_MIGRATIONS_ADD_LEGACY_WODBY1_ENV_VARS marker uses. Verified against util.ValidateUserEnvVarName: WODBY_INIT_ACTION is rejected, WODBY2_SERVICE_INIT_ACTION is allowed.

Must be released before the service manifests switch to the new name, otherwise a manifest would set a variable the deployed image does not read and the init action would silently stop running.

WODBY_* is reserved for platform-owned values, and service manifests may only
define names in it when a privileged user publishes into the Wodby
organizations. Importing such a manifest anywhere else is rejected, which made
the init action unusable outside those orgs.

WODBY2_ is not reserved, so WODBY2_SERVICE_INIT_ACTION can be declared by any
service manifest and imported anywhere.
@csandanov
csandanov merged commit 9b55ad9 into master Aug 22, 2026
37 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant