Environments And Variables

Inspect an Environment

environments get, delete, redeploy, and trigger-build all accept either an environment ID or handle.

Delete an Environment

CRITICAL: Production environments are protected — delete returns a non-zero exit code. Always check the type field via environments get --json before attempting a delete in automation.

Managing Environment Variables

Variables are scoped to a single environment. set and delete require mcloud CLI v0.1.10+.

CRITICAL: Setting or deleting a variable does NOT rebuild or redeploy — the running deployment keeps the old values until you deploy again. For a runtime variable, run mcloud environments redeploy <env>. For a build variable, run mcloud environments trigger-build <env> (a redeploy reuses the existing image and won’t pick up build-variable changes).

List Variables

Filter by type or scope:

Get a Variable

The JSON result exposes environment_id, is_secret, is_build, is_runtime, and source (user or system).

Set a Variable

Create or update variables. The CLI updates when you reference an existing key or a var_... ID, and creates otherwise. Creating or looking up by key requires --project and --environment (or the active context).

New variables default to runtime, non-secret. Control the kind with flags:

Redeploy (runtime) or trigger-build (build) afterward — see the note above.

Delete a Variable

CRITICAL: Deletion is irreversible, and system variables cannot be deleted. Pass --yes in non-interactive environments or the command errors out.

Redeploy or trigger-build afterward for the change to take effect.

Reveal Secret Values

CRITICAL: Only pass --reveal when the user explicitly asks. Plaintext values appear in terminal scrollback, log aggregators, and process listings.

Export to .env

Replicate a Cloud environment’s variables locally with --dotenv, which emits KEY=VALUE lines directly:

CRITICAL: --reveal prints secrets in plaintext. Use it only when the user explicitly asks, and never commit the resulting .env file.