Pulumi Operations: Difference between revisions
Jump to navigation
Jump to search
(→Login) |
|||
| Line 23: | Line 23: | ||
==Login Options== | ==Login Options== | ||
===<tt>-c|--cloud-url</tt>=== | ===<tt>-c|--cloud-url</tt>=== | ||
<font color=darkkhaki>A cloud URL to log in to. Then, what does <code>pulumi login https:/...</code> mean and how is different from the same command with an extra --cloud-url?</font> | |||
===<tt>--local</tt>=== | ===<tt>--local</tt>=== | ||
<code>--local</code> is a shortcut for: | <code>--local</code> is a shortcut for: | ||
Revision as of 04:08, 8 January 2022
External
Internal
Logout
pulumi logout
Login
pulumi login [--cloud-url https://something.example.com]
Without argument, logs into the Pulumi-managed backend. Credentials are cached locally and can be viewed with ~/.pulumi/credentials.json.
State can be maintained in different places, as follows:
- For a "https://" URL, the command line process will access the remote backend via REST.
- For a "file://" URL, the state is managed locally.
- For a "s3://" URL, state is maintained in an S3 bucket.
- For a "gs://" URL, state is maintained in an GCP bucket.
- For a "azblob://" URL, state is maintained in an Azure blob.
Login Options
-c|--cloud-url
A cloud URL to log in to. Then, what does pulumi login https:/... mean and how is different from the same command with an extra --cloud-url?
--local
--local is a shortcut for:
pulumi login file://~
Info
Dumps identity, backend name and URL, Open Directory groups, etc.
pulumi whoami --verbose
This reads ~/.pulumi/credentials.json.
Organization Info
pulumi org ls
pulumi org get <org-name>
Stack Operations
List Stacks
Display the list associated with the current project.
pulumi stack ls
Select a Stack
pulumi stack select
Display Stack Resources
pulumi stack
Display Stack Tags
pulumi stack tag ls
Project Operations
New Project
Create a new project and stack from template.
pulumi new
Plugin Operations
List
pulumi plugin ls
Apply Infrastructure
pulumi up