Channels
announcements
automation-api
aws
azure
blog-posts
built-with-pulumi
cloudengineering
cloudengineering-support
content-share
contribex
contribute
docs
dotnet
finops
general
getting-started
gitlab
golang
google-cloud
hackathon-03-19-2020
hacktoberfest
install
java
jobs
kubernetes
learn-pulumi-events
linen
localstack
multi-language-hackathon
office-hours
oracle-cloud-infrastructure
package-authoring
pulumi-ai
pulumi-cdk
pulumi-cloud
pulumi-crosscode
pulumi-deployments
pulumi-kubernetes-operator
pulumiverse
python
registry
status
testingtesting123
testingtesting321
typescript
welcome
workshops
yaml
Powered by
Title
f
fierce-engine-31599
10/27/2022, 1:15 PM
Hi! I wonder if it's possible to use different state backends with a runtime argument? Currently the only option I saw is to login to the backend and then every action is done against this backend
e
echoing-dinner-19531
10/27/2022, 2:46 PM
You can also set it in the Pulumi.yaml
https://www.pulumi.com/docs/reference/pulumi-yaml/#backend-option
f
fierce-engine-31599
10/28/2022, 8:00 AM
Thank you! Is it possible to set it in the stack configuration as well? Different stacks in the same project use different backends?
e
echoing-dinner-19531
10/28/2022, 9:37 AM
Not at the moment, but feel free to raise a request at
gtihub.com/pulumi/pulumi
for that
3 Views
#general
Join Slack