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

What's not working? Are you looking for the versioning property? And it'd better to use the NEARLINE constant rather than the string, since then you get the hover docs.

Once you enable versioning, you can set up the noncurrent  and max number properties via the lifecycleRules property.

Alright, how do i get the `NEARLINE` as constant?

It should come in the import gcp statement... let me look up the specific file...

Wow, it hasn't been turned into a constant. The string value is used everywhere. It is "NEARLINE", all caps.

<https://github.com/pulumi/pulumi-gcp/search?p=4&amp;q=NEARLINE>

Okay :smile:

So I’ve modified my `lifecycleRules` to this, would this behave like the `Expire noncurrent versions after`, so that all objects within this bucket is deleted after 30 days?

```const bucket = new gcp.storage.Bucket("name", {
  location: "US",
  name: "name",
  storageClass: "NEAERLINE",
  uniformBucketLevelAccess: true,
  versioning: {
    enabled: true,
  },
  lifecycleRules: [
    {
      action: {
        type: "Delete",
      },
      condition: {
        age: 30,
      },
    },
  ],
});```

That'll include current versions, do you want that? Or only non-current versions?

only non-current-versions :slightly_smiling_face:

Then remove `age`, and put in `daysSinceNoncurrentTime`. And probably `numNewerVersions` too.

alright got it:
```  lifecycleRules: [
    {
      action: {
        type: "Delete",
      },
      condition: {
        daysSinceNoncurrentTime: 30,
        numNewerVersions: 2,
      },
    },
  ],```

And that’ll include `Max. Number of versions per object` as well, right?

You'd have to split it into two separate rules for that, I think.

Rules are _or_ed, conditions are _and_ed.

```  lifecycleRules: [
    {
      action: {
        type: "Delete",
      },
      condition: {
        daysSinceNoncurrentTime: 30,
      },
    },
    {
      action: {
        type: "Delete",
      },
      condition: {
        numNewerVersions: 2,
      },
    },
  ],```

Your 1st example means "delete objects that have at least 2 newer versions and haven't been current in at least 30 days".

The second one is "delete objects that haven't been current in 30 days, and delete objects that have at least 2 newer versions (any age)".

Which I think is what your screenshot says, too.

And obv thanks for helping :slightly_smiling_face: