pulumi plugin | CLI commands

Manage language and resource provider plugins

Synopsis

Manage language and resource provider plugins.

Pulumi uses dynamically loaded plugins as an extensibility mechanism for supporting any number of languages and resource providers. The CLI downloads and installs the plugins your project needs automatically, so in most cases you never have to manage them yourself.

The plugin family of commands is for the cases where you do want explicit control: installing plugins ahead of time, for example to warm a cache or to prepare a machine that has no network access at deployment time, inspecting which plugins are installed, or removing ones you no longer need to reclaim disk space.

You may write your own plugins, for example to implement custom languages or resources, although most people will never need to do this. To learn how to write and distribute your own plugins, please see https://www.pulumi.com/docs/iac/guides/building-extending/.

For a list of available resource plugins, please see https://www.pulumi.com/registry/.

pulumi plugin [flags]

Options

  -h, --help   help for plugin

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 - Pulumi command line
• pulumi plugin install - Install one or more plugins
• pulumi plugin list - List plugins
• pulumi plugin remove - Remove one or more plugins from the download cache
• pulumi plugin run - Run a command on a plugin binary