You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
we are implementing S3 Lifecycle policy for our S3 buckets and noticed that all lifecycle policy configuration works as expected except "Expiration" when 'nil' is passed to this field. We are expecting that the Expiration configuration is removed from the rule configuration but the preview shows no objects to be changed. At the same time the "Expiration" works when creating or updating(ex. changing number of days).
we have the same configuration for the "NoncurrentVersionExpiration" but in this case the configuration block works as expected - created, updated and removed.
moreover the "Expiration" configuration is removed if there are another rule changes at the same time. but it is removed silently, preview does not shows any diff for the "Expiration" configuration.
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
The text was updated successfully, but these errors were encountered:
@cooloncoolon it looks like from the about info you are on a previous major version v5. Can you try upgrading to v6 and see if you still have the same issue?
Describe what happened
we are implementing S3 Lifecycle policy for our S3 buckets and noticed that all lifecycle policy configuration works as expected except "Expiration" when 'nil' is passed to this field. We are expecting that the Expiration configuration is removed from the rule configuration but the preview shows no objects to be changed. At the same time the "Expiration" works when creating or updating(ex. changing number of days).
we have the same configuration for the "NoncurrentVersionExpiration" but in this case the configuration block works as expected - created, updated and removed.
moreover the "Expiration" configuration is removed if there are another rule changes at the same time. but it is removed silently, preview does not shows any diff for the "Expiration" configuration.
Sample program
Log output
No response
Affected Resource(s)
s3.NewBucketLifecycleConfigurationV2 Expiration
Output of
pulumi about
CLI
Version 3.132.0
Go Version go1.23.1
Go Compiler gc
Plugins
KIND NAME VERSION
resource aws 5.24.0
language go 3.132.0
resource kubernetes 3.30.2
Host
OS darwin
Version 14.6.1
Arch arm64
This project is written in go: executable='/opt/homebrew/bin/go' version='go version go1.23.1 darwin/arm64'
Dependencies:
NAME VERSION
github.com/lib/pq v1.10.9
github.com/pulumi/pulumi-aws/sdk/v5 v5.24.0
github.com/pulumi/pulumi-kubernetes/sdk/v3 v3.30.2
github.com/pulumi/pulumi/sdk/v3 v3.81.0
github.com/stretchr/testify v1.8.3
Additional context
lifecycle policy configuration declared as follows:
testing rule array
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
The text was updated successfully, but these errors were encountered: