1. Docs
  2. Pulumi CLI
  3. Commands
  4. pulumi env version retract

pulumi env version retract

    Retract a specific revision of an environment


    Retract a specific revision of an environment

    This command retracts a specific revision of an environment. A retracted revision can no longer be read or opened. Retracting a revision also updates any tags that point to the retracted revision to instead point to a replacement revision. If no replacement is specified, the latest non-retracted revision preceding the revision being retracted is used as the replacement.

    The revision pointed to by the latest tag may not be retracted. To retract the latest revision of an environment, first update the environment with a new definition.

    pulumi env version retract [<org-name>/]<environment-name>@<version> [flags]


      -h, --help                  help for retract
          --reason string         the reason for the retraction
          --replace-with string   the version to use to replace the retracted revision

    Options inherited from parent commands

          --color string                 Colorize output. Choices are: always, never, raw, auto (default "auto")
      -C, --cwd string                   Run pulumi as if it had been started in another directory
          --disable-integrity-checking   Disable integrity checking of checkpoint files
      -e, --emoji                        Enable emojis in the output
          --env string                   The name of the environment to operate on.
      -Q, --fully-qualify-stack-names    Show fully-qualified stack names
          --logflow                      Flow log settings to child processes (like plugins)
          --logtostderr                  Log to stderr instead of to files
          --memprofilerate int           Enable more precise (and expensive) memory allocation profiles by setting runtime.MemProfileRate
          --non-interactive              Disable interactive mode for all commands
          --profiling string             Emit CPU and memory profiles and an execution trace to '[filename].[pid].{cpu,mem,trace}', respectively
          --tracing file:                Emit tracing to the specified endpoint. Use the file: scheme to write tracing data to a local file
      -v, --verbose int                  Enable verbose logging (e.g., v=3); anything >3 is very verbose


    Auto generated by spf13/cobra on 13-Jun-2024
      Introducing Pulumi Copilot - Intelligent Cloud Management