But that latter line takes time by installing the gcloud binaries, no?

by using the gcloud github actions, I doubt your

GOOGLE_CREDENTIALS

variable is ever used.

it is not

there are 2 things going on here

taking to DM - hate threads

how can I tell what version of the terraform plugin the pulumi GCP plugin is using?

Hey. I have a Cloud Run revision running with no problems. When I do

pulumi up

to add a new env variable to the container spec, I get this error:

googleapi: Error 409: Conflict for resource 'my-dev-app' for version '123345234100'.

What does this mean? I tried running

pulumi refresh

but that didn't help either. Am I doing something philosophically wrong with my approach?

I'm having the same problem @creamy-engineer-83524. The cloud run service has an option called

AutogenerateRevisionName

which supposedly fixes this issue but I'm finding that I'm still having issues. The GCP audit logs are worthless for troubleshooting this as well. They basically just say "nope"

So i'm putting this into the channel here instead of the thread, because it seems to be a big enough problem that we need some help from the Pulumi devs - it seems there's a problem deploying new revisions of Cloud Run services This issue from the terraform provider appears to be closed, and we appear to be using the version of the provider that has this fix in it: https://github.com/terraform-providers/terraform-provider-google/issues/5898 However, we're still having issues getting 409 conflicts when deploying new revisions of Cloud Run services, even when using

AutogenerateRevisionName

. Can we please get a Pulumi dev to help or weigh in? I'd be glad to get on a video chat and demo the trouble that I'm having

I've posted this issue to GitHub - https://github.com/pulumi/pulumi-gcp/issues/350

the github issue is assigned to someone

is it possible to change bucket perms from fine-grained to uniform?

Hi guys, is there a tutorial how to automate the configuration / deployment for "static website hosting" with google cloud? I am curious because I have not found anything for this topic (and this is so "basic").

I'm hitting GCP read rate limits when I update around a dozen Cloud Run Services at the same time (unfortunately pulumi seems to update services every time, even if there is no change). Is there a way to limit how often pulumi fetches the deploy status for some resources?

Couldn’t find an answer in #python channel asking here https://pulumi-community.slack.com/archives/CDE799L1M/p1591225877028100

not sure if anyone has bumped into this but with the Istio addon on GKE, how can I get the external IP of the ingress gateway? It’s automatically created by GCP so I don’t have the resource in Pulumi to be able to output the load balancer IP. Any ideas?

Hi there, Don’t know if that’s a “feature” but changing the labels of a

NodePool

makes pulumi deleting and recreating the pool … which is obviously not what I want in production…

Previewing update (test):
     Type                          Name                          Plan        Info
     pulumi:pulumi:Stack           est                         
     └─ gcp-clusters:Cluster       cluster                        
 +-     └─ gcp:container:NodePool  cluster-pool-main  replace     [diff: ~nodeConfig]

Did I miss something ? (I literally only added a label. Just to ensure there’s no side effects, if I remove this addition in the code, pulumi don’t ty to update anything anymore)

Hey everyone, two weeks ago I published some higher level gcp components on npm that I was using for a few projects and didn't want to link to the repo. But apparently people have found it as it had 500 downloads this week when I'm sure everyone on my team only used it last week So just to share in case you all find them useful or gives you ideas it is this one here: https://www.npmjs.com/package/pulumi-gcp-components Of course if you wanna help improve it you are all welcome to do so 🙂

anyone had any luck creating a compute instance from a docker container with environment variables?

Hi There! I'm trying to configure continuous deployment with one GCP project per stack, deployed via Github Actions. I'm finding it bit of a pickle trying to figure out where I should store Service Account credentials, and where to configure the logic to switch between them depending on the project. Does anyone know of any examples or literature on this subject?

Hello everyone. Is it possible to resize a gcp’s instance boot disk without replacing it?

Does pulumi support cloud run on anthos gke on-prem?

Does anyone know how to pass the cloud run application url to itself as a config variable? I’d like to use it to generate a cloud run task using this URL.

when i create a

gcp.serviceAccount.Key

, the plaintext key value is only available when the resource is created for the first time. how do i save this to the config as a secret so i can use it later?

In order to namespace resources, using ephemeral projects seems reasonable on GCP. However, the project module does not contain any functionality to create a project straight from pulumi. Has anyone achieve something like that?

Is there a simple way to debug GCP exceptions when doing pulumi up? I tried the -d but it doesn’t tell me which API pulumi is invoking

It doesn’t tell me which api is invoking, so I can’t know which role I am misisng

Pulumi’s GCP SDK requires the

healthChecks

field on

compute.BackendService

but the GCP API disallows any health checks for backend services that a global network endpoint group backend. Disabling TypeScript for that line doesn’t seem to help since the Pulumi SDK checks for presence of this field at runtime. Any thoughts on how to bypass this?