Eron Wright

Along these lines, maybe the [retainOnDelete](https://www.pulumi.com/docs/concepts/options/retainondelete/) option should be passed to the provider, to be able to do a logical cleanup within the provider.

Is this essentially reference counting for ids? We'd persist a map of type+id to ref count (per provider?). Seems to solve the "interruption" case.

Here's a valid use-case where multiple logical resources refer to the same physical resource. A Pulumi YAML program using "patch" resources, with two `ConfigMapPatch` resources pointing to a ConfigMap named...

Any guidance on which repo to open issues into?

This was fixed in https://github.com/pulumi/pulumi-eks/issues/462 by adding a `kubeconfigJson` output property (see https://github.com/pulumi/pulumi-eks/pull/815/commits/f20a0b62670fad1279c3cc5dcd0b84f78d05030d).

@pbelgundi with the suggestion to use DNS to achieve the desired effect, one would need to be careful about SSL hostname verification. My suggestion is to advertise numerous endpoints per...

The issue here is that `SecurityGroup` with inline rules is mutually exclusive with `SecurityGroupRule`. See the [Terraform documentation](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/security_group) which warns against using inline rules in conjunction with rule resources. Please...

The next version of the pulumi-aws provider will emit a warning when the program uses inline rules. The recommendation is to migrate the inline rules to `aws.ec2.SecurityGroupRule` resource(s). Here's a...

Reopening the issue because the first solution - emit a warning - had some pushback in field testing. For example, one of the Pulumi templates triggers the warning: https://github.com/pulumi/templates/blob/98c8a657e2b292343f6dadbbc9fefdc1646fad5d/vm-aws-typescript/index.ts#L57-L74

Related: https://github.com/pulumi/pulumi-aws/issues/3788