-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add PULUMI_BACKEND_URL env var #5789
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lukehoban
added a commit
to pulumi/pulumi-kubernetes-operator
that referenced
this pull request
Nov 20, 2020
Adds a top level `backend` field to the Stack CR that allows pointing all operations for the target Stack at the given backend. In cases where `backend` is set to a non-service backend, the AccessTokenSecret field is also no longer required. This is dependent on pulumi/pulumi#5789, and cannot be merged until the operator can take a dependency on that change in the core `pulumi` CLI. Fixes #83.
The PULUMI_BACKEND_URL env var allows specifying the backend to use instead of deferring to the project or the ~/.pulumi/credentials.json file to decide on the "current" backend. This allows for using Pulumi without a dependence on this piece of global filesystem state, so that each `pulumi` invocation can control the exact backend it want's to operate on, without having to do stateful `pulumi login`/`pulumi logout` operations. This is especially useful for automation scenarios like Automation API generally (and effectively solves #5591), or pulumi/pulumi-kubernetes-operator#83 specifically. This also makes things like https://github.com/pulumi/pulumi/blob/efe7a599e65637378b9ceeac125386b5effd0d68/dist/actions/entrypoint.sh#L10 less necessary, and possible to accomplish for any containerized `pulumi` execution without the need for this logic to be embedded in bash scripts wrapping the CLI.
e297138
to
2f76217
Compare
leezen
approved these changes
Nov 20, 2020
lukehoban
added a commit
to pulumi/pulumi-kubernetes-operator
that referenced
this pull request
Dec 3, 2020
Adds a top level `backend` field to the Stack CR that allows pointing all operations for the target Stack at the given backend. In cases where `backend` is set to a non-service backend, the AccessTokenSecret field is also no longer required. This is dependent on pulumi/pulumi#5789, and cannot be merged until the operator can take a dependency on that change in the core `pulumi` CLI. Fixes #83.
lukehoban
added a commit
to pulumi/pulumi-kubernetes-operator
that referenced
this pull request
Dec 3, 2020
Adds a top level `backend` field to the Stack CR that allows pointing all operations for the target Stack at the given backend. In cases where `backend` is set to a non-service backend, the AccessTokenSecret field is also no longer required. This is dependent on pulumi/pulumi#5789, and cannot be merged until the operator can take a dependency on that change in the core `pulumi` CLI. Fixes #83.
This was referenced Dec 30, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
PULUMI_BACKEND_URL
env var allows specifying the backend to use instead of deferring to the project or the~/.pulumi/credentials.json
file to decide on the "current" backend. This allows for using Pulumi without a dependence on this piece of global filesystem state, so that eachpulumi
invocation can control the exact backend it want's to operate on, without having to do statefulpulumi login
/pulumi logout
operations.This is especially useful for automation scenarios like Automation API generally (and effectively solves #5591), or pulumi/pulumi-kubernetes-operator#83 specifically.
This also makes things like
pulumi/dist/actions/entrypoint.sh
Line 10 in efe7a59
pulumi
execution without the need for this logic to be embedded in bash scripts wrapping the CLI.