GCP Cloud Storage Object Lifecycle Management not deleting old versions as expected
I'm upgrading from an older version and I'm stuck trying to I've searched everywhere and can't find a clear answer... I've set up an object versioning policy in GCP Cloud Storage to automatically delete older versions of objects after 30 days, but it seems like the lifecycle management is not working as expected. Despite having the following configuration in my bucket's lifecycle management settings: ```json { "lifecycle": { "rule": [ { "action": { "type": "Delete" }, "condition": { "age": 30, "isLive": false } } ] } } ``` I have uploaded several versions of an object and waited more than 30 days, but the old versions are still there. I've verified that the bucket indeed has versioning enabled, and I can see the old versions when I list objects using the GCP console and `gsutil` commands. I tried running `gsutil lifecycle get gs://my-bucket` to check if the lifecycle configuration is applied correctly, and it matches what I set. Also, I checked the IAM roles, and the service account has the necessary permissions, including `Storage Admin`. Interestingly, when I manually delete a non-current version of an object, it works fine. However, I'm looking for an automated solution to manage these versions, especially since my bucket holds a lot of data. Has anyone faced a similar scenario with Cloud Storage lifecycle management not triggering deletions for older versions? Any ideas on what could be going wrong or how to troubleshoot this effectively? This is part of a larger API I'm building. Any help would be greatly appreciated! I'm coming from a different tech stack and learning Json. Any suggestions would be helpful. I've been using Json for about a year now. Any ideas how to fix this?