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
Title
g
gray-belgium-81846
07/12/2021, 9:18 PMIs it bad form to read env vars from pulumi programs? I’m calling a pulumi program from my CI system, and I’d like to be able to pass the build #. I debated setting it as Configuration, but I don’t want to update the stack’s yaml file as part of CI.
b
billowy-army-68599
07/12/2021, 9:31 PMno that's a totally legit way of doing it!
that's the joy of being able to use regular programming languages, but you do need to be careful - the build # will change every time which means your pulumi program will update every time
g
gray-belgium-81846
07/12/2021, 9:40 PMThanks. In this case the CI job is updating an ECS task revision that includes the build #, so update is expected.