dcloud deploy env secure

Move plain variables into secrets, without the values leaving the platform

IAM deploy:ManageEnvChanges stateAsks before it deletes (-y skips)

Each named variable must hold a plain value. Its value becomes a new secret under a KMS key, granted to the deploy consumer and bound to the variable in one transaction; the plain value is no longer stored. Security Posture offers this as the fix for a credential kept as a plain variable. Saving does not restart the app. Pass redeploy: true to roll the live deployment’s own source onto the new configuration (also needs deploy:DeployApp); otherwise the response and GET …/env report pending until someone redeploys.

Synopsis

dcloud deploy env secure id --keys keys [flags]

Arguments

  • <id>Required

    string

    Also accepted as --id. Constraints: uuid

Flags

  • --keysRequired

    array of string

    Plain variables whose values move into new secrets

    Constraints: 1-128 chars, /^[A-Za-z_][A-Za-z0-9_]*$/

  • --key-idOptional

    string

    KMS key the new secrets are encrypted under; default the organization’s default key

    Constraints: uuid

    May be null.

  • --redeployOptional

    boolean (--redeploy / --no-redeploy)

    Also roll the live deployment onto the new environment; default false

Example

dcloud deploy env secure id --keys '["example"]'

Generated from the API description, the same one the API checks requests against and the CLI is built from.