RFC: Exclusive Relationship Management Resources Support #4772
Labels
kind/engineering
Work that is not visible to an external user
kind/enhancement
Improvements or new features
Pulumi AWS provider should withhold input property deprecations introduced by the Terraform AWS provider until Pulumi-specific issues on the intended upgrade path are resolved.
The affected properties include (see 39376 for a full list):
aws.iam.Role
managedPolicyArns
aws.iam.Role
inlinePolicies
The latest iteration of Terraform AWS provider design thinking is introducing exclusive relationship management resources. To illustrate on the
aws.iam.Role
resource:inline_policy
repeated argument in favor of N relationship resources such asaws_iam_role_policy
aws_iam_role_policy
resources in Terraform does not guarantee that the associatedaws_iam_role
has no policies in the cloud that are not being tracked, something thatinline_policy
used to guaranteeaws_iam_role_policies_exclusive
is introduced: if users list allaws_iam_role_policy
inaws_iam_role_policies_exclusive
then Terraform will proactively detect when the actual set of policies in the cloud does not match the one specified byaws_iam_role_policies_exclusive
Unfortunately when testing this upgrade scenario in the Pulumi provider we found that
aws.iam.RolePoliciesExclusive
does not detect role policy drift due to specifics of how Pulumi maps Terraform providers (#4766).Because of this issue, users trying to act on the deprecation notice in Pulumi will not be able to rely on
aws.iam.RolePoliciesExclusive
to ensure all inline policies are tracked in Pulumi. Other property deprecations are likely similarly affected.The proposal going forward is as follows:
References
The text was updated successfully, but these errors were encountered: