1. Docs
  2. Pulumi CLI
  3. Commands
  4. pulumi plugin

pulumi plugin

    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. These plugins are distributed out of band and must be installed manually. Attempting to use a package that provisions resources without the corresponding plugin will fail.

    You may write your own plugins, for example to implement custom languages or resources, although most people will never need to do this. To understand how to write and distribute your own plugins, please consult the relevant documentation.

    The plugin family of commands provides a way of explicitly managing plugins.

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

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

    Auto generated by spf13/cobra on 22-Jun-2024
      Introducing Pulumi Copilot - Intelligent Cloud Management