Channels
pulumi-ai
package-authoring
pulumi-cdk
oracle-cloud-infrastructure
learn-pulumi-events
linen
registry
built-with-pulumi
pulumi-cloud
contribex
testingtesting321
hacktoberfest
cloudengineering
yaml
pulumi-crosscode
content-share
finops
multi-language-hackathon
office-hours
workshops
blog-posts
localstack
welcome
gitlab
pulumi-kubernetes-operator
jobs
aws
pulumi-deployments
dotnet
golang
announcements
java
pulumiverse
python
install
getting-started
cloudengineering-support
testingtesting123
hackathon-03-19-2020
typescript
google-cloud
contribute
azure
kubernetes
docs
automation-api
status
general
Powered by
Title
w
worried-queen-62794
04/13/2021, 2:08 AM
Is there a way to ensure that a stack is using the correct backend? Having to remember to log in and out all the time is very error prone.
Or is the backend available via the API somewhere?
r
red-match-15116
04/13/2021, 2:12 AM
You can set the backend as a project-level setting with the
backend.url
key in
Pulumi.yaml
or as an operation-level setting with the
PULUMI_BACKEND_URL
env var
.
w
worried-queen-62794
04/13/2021, 2:12 AM
Cool thanks
w
white-balloon-205
04/13/2021, 2:38 AM
We are also likely to start storing the backend info in the stack file in the future to address this scenario even more directly.
https://github.com/pulumi/pulumi/issues/2996
is an issue tracking this.
👍 2
#general
Join Slack