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.

Pulumi Community

can you share the full program so we can repro? my first guess is that setting the value to `False` and then a value for the rule_visibility is probably mutually exclusive

This is part of some confidential code so me sharing the whole code would be very tough. However, I tried setting enable to true and removed rule_visibility, same error. 

The command I use is Pulumi up. And then I get the whole cluster except for this error. 

do you have a minimal repro of just these resources? it’s going to be difficult to debug without a repro

ah, wait. Which version of the gcp provider are you using?

Client is 1.27. And server is 1.25

I got this by running kubectl version. 

that’s not the pulumi gcp provider version

Pulumi &gt;= 3.0.0, &lt; 4.0.0
Pulumi-gcp == 6.39.0
Pulumi-random &gt;= 4.0.0, &lt;5.0.0
Google-api-Python-client==2.86.0

there was a bug in this resource fixed in `6.40.0` of the provider :slightly_smiling_face:
If you do
```pip3 install pulumi-gcp --upgrade```
It’ll likely fix it :slightly_smiling_face:

I’ll respond on StackOverflow too :slightly_smiling_face:

<https://stackoverflow.com/a/76585609/645002>

I changed the version to 6.41.0 and still the command “Pulumi up” fails with the same errror. 

You wil need to run a successful up operation with the new provider. So:
Remove the offending broken config
Update the provider SDK
Run a Pulumi up
Readd the config 

I destroyed the whole cluster and reinstalled it after upgrading to the latest Pulumi-gcp version. 

Okay you’ll need to file a GitHub issue then I’m afraid 

Sorry, I meant, it worked. After I destroyed the cluster and upgraded to the latest one, it worked!

Thanks <@UCWG26BH7> for all your help. 