pulumi plugin list | CLI commands

List plugins

Synopsis

List plugins.

This command lists the plugins in the local plugin cache: the plugins directory under your $PULUMI_HOME directory, ~/.pulumi by default. It shows the size, install time, and last use of each.

Plugins bundled with the Pulumi CLI are installed next to the pulumi binary rather than in the cache, so they are not listed. This includes the language hosts for Node.js, Python, Go, .NET, Java, and YAML. A language plugin that is not bundled, such as HCL, is cached like any other plugin and does appear.

Use –project (-p) to list the plugins the current project requires instead. Those are resolved the way the CLI would load them, so bundled language hosts do appear; plugins that are not installed are omitted.

Use –output json to emit the list as JSON.

pulumi plugin list [flags]

Options

  -h, --help            help for list
      --output string   Output format. Supported values are: default and json (default "default")
  -p, --project         List only the plugins used by the current project

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:// or https:// 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 plugin - Manage language and resource provider plugins