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
Title
a
astonishing-gpu-28317
03/07/2022, 5:07 PMdoes anyone use cloud build to deploy cloud run? we add environment variables during build that aren’t knowable during pulumi up, e.g. the code version being deployed. this causes problems because when we run
pulumi upg
great-queen-39697
03/07/2022, 11:23 PMSo caveat that I haven't used Cloud Build with Pulumi just yet. However, are the variables that aren't knowable during pulumi up defined in code somewhere that you could reference the same code with your Pulumi program?
a
astonishing-gpu-28317
04/04/2022, 7:53 PMthey’re things like the build tag, which aren’t knowable until the build is run, which is after code has been committed
g
great-queen-39697
04/04/2022, 8:46 PMahh, got it. Looks like there's some default substitutions; they all should be available to your Pulumi program just as they would be for any of your code: https://cloud.google.com/build/docs/configuring-builds/substitute-variable-values. They'd then get set with this key: https://www.pulumi.com/registry/packages/gcp/api-docs/cloudbuild/trigger/#substitutions_python (I've got it set to Python for me, but you can flip to another language with the language switcher at the top of the page)
And then I think I'd call them as outputs to get passed to Cloud Run. If you set the
dependsOngcp.cloudbuild.Trigger(..., substitutions={"_VERSION": "blah"}, ...)
gcp.cloudrun.Service(..., template=gcp.cloudrun.ServiceTemplateArgs(spec=gcp.cloudrun.ServiceTemplateSpecArgs(containers=[gcp.cloudrun.ServiceTemplateSpecContainerArgs(image=<from above>, ...)], ...), ...), ...)a
astonishing-gpu-28317
04/04/2022, 9:23 PMbrilliant, this should work for our use case, thanks a ton @great-queen-39697!
hmm, another issue seems to be the Image attribute (cloudrun.ServiceTemplateSpecContainerArgs.Image) - cloud build sets it to a concrete image value (e.g. us.gcr.io/myproject/myservice:some-hash) which i dont think i can get prior to build
g
great-queen-39697
04/05/2022, 1:29 AMAh, I'm pretty sure that's an output you get from running the cloudbuild step (meaning it's returned as a Pulumi output). Try appending something like this (this is Python), assuming you assign the cloudbuild.trigger call to a variable `image`:
pulumi.export('id', image.id)