Skip to main content
Sign in Dashboard Get started
  1. Docs
  2. Infrastructure as Code
  3. Pulumi CLI
  4. Commands
  5. pulumi about | CLI commands

pulumi about | CLI commands

Generated for Pulumi CLI v3.245.0.

    Print information about the Pulumi environment.

    Synopsis

    Print information about the Pulumi environment.

    Prints out information helpful for debugging the Pulumi CLI. This includes information about:

    • the CLI and how it was built
    • which OS Pulumi was run from
    • the current project
    • the current stack
    • the current backend
    pulumi about [flags]

    Options

      -h, --help           help for about
  -j, --json           Emit output as JSON
  -s, --stack string   The name of the stack to get info on. Defaults to the current stack
  -t, --transitive     Include transitive dependencies

    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