1. Docs
  2. Pulumi CLI
  3. Commands
  4. pulumi stack select

pulumi stack select

    Switch the current workspace to the given stack

    Synopsis

    Switch the current workspace to the given stack.

    Selecting a stack allows you to use commands like config, preview, and update without needing to type the stack name each time.

    If no argument is supplied, you will be prompted to select one interactively. If provided stack name is not found you may pass the –create flag to create and select it

    pulumi stack select [<stack>] [flags]
    

    Options

      -c, --create                    If selected stack does not exist, create it
      -h, --help                      help for select
          --secrets-provider string   Use with --create flag, The type of the provider that should be used to encrypt and decrypt secrets
                                      (possible choices: default, passphrase, awskms, azurekeyvault, gcpkms, hashivault) (default "default")
      -s, --stack string              The name of the stack to select
    

    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
      -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
    

    SEE ALSO

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