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

I'm seeing some unexpected behaviour managing s3 events with `bucket.onObjectCreated` and `bucket.onObjectRemoved`.
If I have multiple events defined (which is perfectly valid in s3), removing 1 removes them ALL. Is this a known bug?

I found a work-around to define a single `aws.s3.BucketNotification` with all the events - but this is not really intuitive, particularly given that defining multiple succeeds, but leaves an expected state - the last one wins, and others are deleted, but pulumi says all is fine.

That sounds like a bug.

Could you open an issue in <https://github.com/pulumi/pulumi-aws> with the repro?