pulumi plugin install

Install one or more plugins

Synopsis

Install one or more plugins.

This command is used to manually install plugins required by your program. It may be run with a specific KIND, NAME, and optionally, VERSION, or by omitting these arguments and letting Pulumi compute the set of plugins required by the current project. When Pulumi computes the download set automatically, it may download more plugins than are strictly necessary.

If VERSION is specified, it cannot be a range; it must be a specific number. If VERSION is unspecified, Pulumi will attempt to look up the latest version of the plugin, though the result is not guaranteed.

pulumi plugin install [KIND NAME [VERSION]] [flags]

Options

      --checksum string   The expected SHA256 checksum for the plugin archive
      --exact             Force installation of an exact version match (usually >= is accepted)
  -f, --file string       Install a plugin from a binary, folder or tarball, instead of downloading it
  -h, --help              help for install
      --reinstall         Reinstall a plugin even if it already exists
      --server string     A URL to download plugins from

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

• pulumi plugin - Manage language and resource provider plugins

Auto generated by spf13/cobra on 4-Oct-2024