pulumi stack get | CLI commands

[EXPERIMENTAL] Retrieve detailed information about a stack

Synopsis

[EXPERIMENTAL] Retrieve detailed information about a stack.

Shows the current stack’s state: the owning organization, the resources in the stack, stack outputs, the last update, and (on the Pulumi Cloud backend) any in-progress operation. This is the same information shown by pulumi stack

pulumi stack get [flags]

Options

  -h, --help            help for get
      --output string   Output format. Supported values are: default and json (default "default")
  -i, --show-ids        Display each resource's provider-assigned unique ID
      --show-name       Display only the stack name
      --show-secrets    Display stack outputs which are marked as secret in plaintext
  -u, --show-urns       Display each resource's Pulumi-assigned globally unique URN
  -s, --stack string    The name of the stack to operate on. Defaults to the current stack

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
      --otel-traces string           Export OpenTelemetry traces to the specified endpoint. Use file:// for local JSON files, grpc:// for remote collectors
      --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

• pulumi stack - Manage stacks and view stack state