Skip to main content
  1. Docs
  2. pulumi env settings get | CLI commands

pulumi env settings get | CLI commands

Generated for Pulumi CLI v3.245.0.

    Get environment settings

    Synopsis

    Get environment settings

    This command gets environment settings. If no setting name is provided, all settings are returned. Otherwise, only the specified setting value is returned.

    Available settings: deletion-protected Enable or disable deletion protection

    pulumi env settings get [<org-name>/][<project-name>/]<environment-name> [<setting-name>] [flags]
    

    Options

      -h, --help            help for get
          --output string   output format: "text" (default) or "json" (default "text")
    

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