Come join Pulumi for the industry's first Cloud Engineering Summit! October 7–8. Save Your Spot

pulumi login

Log in to the Pulumi service

Synopsis

Log in to the Pulumi service.

The service manages your stack’s state reliably. Simply run

$ pulumi login

and this command will prompt you for an access token, including a way to launch your web browser to easily obtain one. You can script by using PULUMI_ACCESS_TOKEN environment variable.

By default, this will log in to the managed Pulumi service backend. If you prefer to log in to a self-hosted Pulumi service backend, specify a URL. For example, run

$ pulumi login https://api.pulumi.acmecorp.com

to log in to a self-hosted Pulumi service running at the api.pulumi.acmecorp.com domain.

For https:// URLs, the CLI will speak REST to a service that manages state and concurrency control. [PREVIEW] If you prefer to operate Pulumi independently of a service, and entirely local to your computer, pass file://<path>, where <path> will be where state checkpoints will be stored. For instance,

$ pulumi login file://~

will store your state information on your computer underneath ~/.pulumi. It is then up to you to manage this state, including backing it up, using it in a team environment, and so on.

As a shortcut, you may pass –local to use your home directory (this is an alias for file://~):

$ pulumi login --local

[PREVIEW] Additionally, you may leverage supported object storage backends from one of the cloud providers to manage the state independent of the service. For instance,

AWS S3:

$ pulumi login s3://my-pulumi-state-bucket

GCP GCS:

$ pulumi login gs://my-pulumi-state-bucket

Azure Blob:

$ pulumi login azblob://my-pulumi-state-bucket
pulumi login [<url>] [flags]

Options

  -c, --cloud-url string   A cloud URL to log in to
  -h, --help               help for login
  -l, --local              Use Pulumi in local-only mode

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
      --logflow                      Flow log settings to child processes (like plugins)
      --logtostderr                  Log to stderr instead of to files
      --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 21-Sep-2020