This message was deleted.

did their API change:

/v1beta1/projects/[project_name]/locations/europe-west1-b/clusters/projects/[project_name]/locations/europe-west1-b/clusters/[cluster_name]/nodePools

maybe out of beta? I’m not working on GCP, so I can’t help concretely, but: First: make a backup of your stack and don’t touch it

pulumi stack export > backup.<stack>.$(date +'%s').export

. The problem is most likely that the old urls aren’t active anymore, but the old provider is still referenced in your stack. verify that

npm outdated

(or whatever language you use) really doesn’t offer more updates. Try now if a

pulumi refresh

helps. This just changes the stack, not the resources. If you’re lucky, you should be good after this. Especially if it’s a leaf resource and not a complex composite (which should be the case here): delete the resource from the stack

pulumi state delete <urn>

and then edit your stack (eg. in TS

new <the resource>(<name>, { <args>}, { import: ["<import id>"]})

. I’m assuming for GCP they also use the TF bridge, so the <import id> you can find at the bottom of the Terraform GCP provider page. The import only works if there are no changes, so you might have to fiddle with your resources args. If you still have the problem, it gets hairy. You can: • verify that your gcloud install is up to date. IIRC pulumi doesn’t use it, but I’m not 100% sure. Try

pulumi up

again. • copy the stack export, manually (sed/vim, whatever) modify it to use the new provider version, and then import it with

pulumi stack import

. I don’t think you’ll see the url referenced directly in the stack, that should be hidden behind the provider. • to help with the above and further debugging, try to figure out how it looks like/works if you create a new one resource of the same type and inspect the stack export of it. • If you run eg

pulumi up

, as a last ditch effort you can also turn on full debug output with

-v=9 --logtostderr

, to find out why the calls differ between the old and the new stack (the output is quite messy, but if all else fails.

@brash-manchester-88595 thanks, that’s a very detailed answer ! Unfortunately everything is already up to date (yes i use

npm

) and I don’t have any other log than this 404 from google (even with full debug on). I have this error while creating a new stack (new gke cluster) from my code so editing the stack is useless since the resource is not created. If I

pulumi up

an existing stack (gke cluster) I don’t have any error though.

did you check that the API is enabled?

this code and the project using it didn’t change since at least a year, already provisioned and regularly updated a few clusters with it without any issue so far.

Sorry for the delay @faint-motherboard-95438 - I'm taking a look at this now and will report back anything I can find on the issue.

@white-balloon-205 thanks for your help. That’s concerning, and not the first time I had such issue since a year, a code which was working fine one day breaks the next one. Especially when this code is used to maintain production services. I’ve actually made another post directly related https://pulumi-community.slack.com/archives/C84L4E3N1/p1580988033025000 about how to ensure such problem does not happen at critical times and be able to detect and fix a breaking change coming from outside.