Pulumi

Concepts

Packages

Commands (CLI)

Cancel

Config

Destroy

Logout

Logs

New

Plugin

Preview

Refresh

Stack

Update

Cloud Console

Continuous Deployment

Pulumi Vs. Others

FAQ

Change Log

Edit This Page

Log into the Pulumi service

Synopsis

Log into 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 into app.pulumi.com. If you prefer to log into a separate instance of the Pulumi service, such as Pulumi Enterprise, specify a . For example, run

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

to log in to a Pulumi Enterprise server running at the pulumi.acmecorp.com domain.

For https:// URLs, the CLI will speak REST to a service that manages state and concurrency control. If you prefer to operate Pulumi independently of a service, and entirely local to your computer, pass file://, where 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

pulumi login [<url>] [flags]

Options

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

Options inherited from parent commands

      --color colors.Colorization    Colorize output. Choices are: always, never, raw, auto (default always)
  -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 (default true)
      --logflow                      Flow log settings to child processes (like plugins)
      --logtostderr                  Log to stderr instead of to files
      --profiling string             Emit CPU and memory profiles and an execution trace to '[filename].[pid].{cpu,mem,trace}', respectively
      --tracing string               Emit tracing to a Zipkin-compatible tracing endpoint
  -v, --verbose int                  Enable verbose logging (e.g., v=3); anything >3 is very verbose

Synopsis

Options

Options inherited from parent commands

SEE ALSO

Auto generated by spf13/cobra on 16-Oct-2018