126d31c9c2
As part of making the local backend more prominent, this changes a few aspects of how you use it: * Simplify how you log into a specific cloud; rather than `pulumi login --cloud-url <url>`, just say `pulumi login <url>`. * Use a proper URL scheme to denote local backend usage. We have chosen file://, since the REST API backend is of course always https://. This means that you can say `pulumi login file://~` to use the local backend, with state files stored in your home directory. Similarly, we support `pulumi login file://.` for the current directory. * Add a --local flag to the login command, to make local logins a bit easier in the common case of using your home directory. Just say `pulumi login --local` and it is sugar for `pulumi login file://~`. * Print the URL for the backend after logging in; for the cloud, this is just the user's stacks page, and for the local backend, this is the path to the user's stacks directory on disk. * Tidy up the documentation for login a bit to be clearer about this. This is part of pulumi/pulumi#1818. |
||
|---|---|---|
| .. | ||
| backend.go | ||
| crypto.go | ||
| display.go | ||
| jsonmessage.go | ||
| progress.go | ||
| rows.go | ||
| snapshot.go | ||
| stack.go | ||
| state.go | ||