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 paste the full code where you’re creating a bucket?

Additionally, please paste the output of:
```pip freeze | grep pulumi```
run from venv associated with Pulumi project.

```bucket = gcp.storage.Bucket("flytebucket",
 public_access_prevention=True,
)```

image.png

you have no `pulumi-gcp` visible in `pip freeze` output - that’s weird

the code itself looks good (assuming you have proper GCP setup with default location, project etc. it should work)

I asked about `pip freeze` to check what version of `pulumi-gcp` you’re trying to use. Are you sure you listed the correct venv?

Hey <@U0288KYUB7C> yes there was pulumi-gcp version issue. I have updated the version.
It does not anymore say that --&gt; got an unexpected keyword argument 'public_access_prevention'
Now the error is different.
If I am writing bool value: True it says--&gt;
 error: 1 error occurred:
        * updating urn:pulumi:flytetest::flyte-spark::gcp:storage/bucket:privatebucket: 1 error occurred:
        * googleapi: Error 400: Invalid value for: 1 is not a valid value, invalid

If I am giving str value: "True" the error is--&gt;  Invalid value for: True is not a valid value, invalid

The code is this:
static = gcp.storage.Bucket("privatebucket",
location="us-central1",
public_access_prevention=True
)
Pulumi versions are attached.

Yeah, not it makes sense at least :slightly_smiling_face: (I first wanted to get rid of “wtf class error”, now we can talk about details).

I saw in the type hints that it expects `str` instead of `bool` but it was unrelated to the issue you had before. Let me see what it accepts.

<https://cloud.google.com/storage/docs/public-access-prevention>

&gt; Even if a bucket does not have public access prevention explicitly enforced in its settings, it might still inherit public access prevention, which occurs if the organization policy constraint `storage.publicAccessPrevention` is set on the project, folder, or organization that the bucket exists within. For this reason, the bucket state *can only be set to `enforced` or `inherited`.*