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

Humm, is there a way to *update* a security group rather than *replace* it when modifying ingress / egress rules?

I've got a group that I imported, and I want to modify it, but it's not acceptable to have some in-between state where the EC2 instances don't have any security group applied. The instances are unfortunately not in Pulumi's control, and probably shouldn't be either (as they are created by a lambda deployed via a CF template by a vendor).

Can you elaborate on this -_"where the EC2 instances don't have any security group applied"_?

In general, a SecurityGroup should not need to be replaced when modifying ingress or egress rules. Can you share the output of `pulumi preview --diff`?

Ah, I just realized the issue.. I tried to change the description of the security group. If I don't, then it looks fine.