Skip to main content
Pulumi logo Pulumi logo
  1. Docs
  2. Infrastructure as Code
  3. Pulumi CLI
  4. Commands
  5. pulumi logout | CLI commands

pulumi logout | CLI commands

Generated for Pulumi CLI v3.259.0.

    Log out of a Pulumi state backend

    Synopsis

    Log out of a Pulumi state backend.

    This command deletes the credentials stored on this machine for a single login. With no arguments, it logs you out of the current backend:

    $ pulumi logout
    

    You can be logged in to several backends at once. To choose one, pass its URL, written the same way you wrote it when logging in:

    $ pulumi logout https://api.pulumi.acmecorp.com
    $ pulumi logout s3://my-pulumi-state-bucket
    

    To log out of every backend at once, pass --all:

    $ pulumi logout --all
    

    --local is a shortcut for file://~, matching pulumi login --local.

    pulumi logout [url] [flags]
    

    Options

          --all                Log out of all backends
      -c, --cloud-url string   A cloud URL to log out of (defaults to the current backend)
      -h, --help               help for logout
      -l, --local file://~     Log out of local-only mode (an alias for file://~)
    

    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
          --otel-traces string           Export OpenTelemetry traces to the specified endpoint. Use file:// for local JSON files, grpc:// or https:// 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

      The infrastructure as code platform for any cloud.