Skip to main content
Sign in Dashboard Get started
  1. Docs
  2. pulumi deployment run | CLI commands

pulumi deployment run | CLI commands

Generated for Pulumi CLI v3.242.0.

    Launch a deployment job on Pulumi Cloud

    Synopsis

    Launch a deployment job on Pulumi Cloud

    This command queues a new deployment job for any supported operation of type update, preview, destroy, refresh, detect-drift or remediate-drift.

    pulumi deployment run <operation> [url] [flags]

    Options

          --agent-pool-id string                   The agent pool to use to run the deployment job. When empty, the Pulumi Cloud shared queue will be used.
      --env --env FOO=bar                      Environment variables to use in the remote operation of the form NAME=value (e.g. --env FOO=bar)
      --env-secret --env FOO=secret            Environment variables with secret values to use in the remote operation of the form NAME=secretvalue (e.g. --env FOO=secret)
      --executor-image string                  The Docker image to use for the executor
      --executor-image-password string         The password for the credentials with access to the Docker image to use for the executor
      --executor-image-username string         The username for the credentials with access to the Docker image to use for the executor
      --git-auth-access-token string           Git personal access token
      --git-auth-password string               Git password; for use with username or with an SSH private key
      --git-auth-ssh-private-key string        Git SSH private key; use --git-auth-password for the password, if needed
      --git-auth-ssh-private-key-path string   Git SSH private key path; use --git-auth-password for the password, if needed
      --git-auth-username string               Git username
      --git-branch string                      Git branch to deploy; this is mutually exclusive with --git-commit; either value needs to be specified
      --git-commit string                      Git commit hash of the commit to deploy (if used, HEAD will be in detached mode); this is mutually exclusive with --git-branch; either value needs to be specified
      --git-repo-dir string                    The directory to work from in the project's source repository where Pulumi.yaml is located; used when Pulumi.yaml is not in the project source root
  -h, --help                                   help for run
      --inherit-settings                       Inherit deployment settings from the current stack (default true)
      --pre-run-command stringArray            Commands to run before the remote operation
      --skip-install-dependencies              Whether to skip the default dependency installation step
  -s, --stack string                           The name of the stack to operate on. Defaults to the current stack
      --suppress-permalink                     Suppress display of the state permalink
      --suppress-stream-logs                   Suppress log streaming of the deployment job (default true)

    Options inherited from parent commands

          --color string                 Colorize output. Choices are: always, never, raw, auto (default "auto")
      --config-file string           Override the file name where the deployment settings are specified. Default is Pulumi.[stack].deploy.yaml
  -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