after updating to 6.69, I can not preview and up .

[a523]

Describe what happened

when I run pulumi preview

 aws:s3:BucketLifecycleConfigurationV2 (xxxxx):
    error: objectEncoder failed on property "rule": encList failed while encoding element 0 ({map[abortIncompleteMultipartUpload:{<nil>} expiration:{<nil>} filter:{map[and:{<nil>} objectSizeGreaterThan:{} objectSizeLessThan:{} prefix:{} tag:{<nil>}]} id:{transfer_to_cold_storage} noncurrentVersionExpiration:{<nil>} noncurrentVersionTransitions:{[]} prefix:{} status:{Enabled} transitions:{[{map[date:{} days:{90} storageClass:{STANDARD_IA}]}]}]}): objectEncoder failed on property "filter": objectEncoder failed on property "object_size_greater_than": Expected a Number

How to fix it ?

Sample program

It is easy to reproducible :

1. using the old version pulumi-aws to create bucket with a LifecycleConfigurationV2 an rule like this:

lifecycle_rules = [
    {
        "id": "transfer_to_cold_storage",
        "filter": {},   # this is empty
        "transitions": [
            {
                "storage_class": "STANDARD_IA",
                "days": 90,
            }
        ],
        "status": "Enabled",
    }
]

2. update to 6.69
3. run pulumi preview --refresh

Log output

No response

Affected Resource(s)

No response

Output of pulumi about

CLI
Version 3.133.0
Go Version go1.23.1
Go Compiler gc

Plugins
KIND NAME VERSION
resource aws 6.69.0
language python 3.133.0
resource random 4.16.1

Host
OS darwin
Version 13.6.1
Arch x86_64

This project is written in python: executable='xxxxx' version='3.11.11'

Backend
Name xxx
URL s3://xxxxx-pulumi-backend-hkxxxxxx
User xxxx
Organizations
Token type personal

Dependencies:
NAME VERSION
boto3 1.34.133
pulumi_aws 6.69.0
pulumi_random 4.16.1
setuptools 65.5.1
wheel 0.38.4

Pulumi locates its logs in /var/folders/gd/tqy86p5n2cq64p0wghxk2w400000gn/T/ by default
warning: Failed to get information about the current stack: No current stack

Additional context

No response

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).

[corymhall]

@a523 thanks for raising this issue! I've been able to track it down and created an issue for the root cause.

We'll need to work on figuring out how to fix the root cause or implement a patch fix here. Until then the only workaround that you can try is to edit the state to update the objectSizeGreaterThan and objectSizeLessThan values to null. Our permanent fix should make this change to the state for you as part of a state upgrader.