This message was deleted.

sparse-intern-71089

06/13/2022, 7:45 PM

This message was deleted.

great-queen-39697

06/13/2022, 9:40 PM

Unfortunately, I suspect this might be an error upstream. Someone filed a similar issue: https://github.com/pulumi/pulumi-google-native/issues/418 Are you able to add the pool via the gcloud CLI? If you can, then it might be something with the underlying API from upstream. If you can't, it might give you a better error code (there's some spots where our native provider is giving a generic code as it's still in beta, and we want to fix those)

ancient-rose-25146

06/13/2022, 9:43 PM

I was able to add the node pool via the cli, and if I did

pulumi up

on a completely new stack it would let me do that as well. The problem was only from updating a currently existing cluster via pulumi.

great-queen-39697

06/13/2022, 9:44 PM

Oh, interesting. Let me go digging for a sec; one minute

great-queen-39697

06/13/2022, 9:57 PM

That really seems like a bug. Can you open an issue in the native provider, please? https://github.com/pulumi/pulumi-google-native/issues/new?assignees=&labels=kind%2Fbug%2Cneeds-triage&template=bug.yaml

great-queen-39697

06/13/2022, 9:58 PM

I can't pinpoint it in the schema, but it's likely there's an error message getting swallowed.

ancient-rose-25146

06/13/2022, 9:58 PM

Sure when I get the time I will do just that.

great-queen-39697

06/13/2022, 9:58 PM

Thank you!

2 Views

Open in Slack

Previous Next

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.