Only add IAM condition fields to IAM resources if the API supports IAM conditions #18412
Labels
breaking-change
mmv1-generator
Provider-wide changes to resource templates or other generator changes
service/terraform
size/xl
technical-debt
Milestone
What kind of contribution is this issue about?
MMv1-based resource
Details
Currently, all IAM resources have condition fields - but they are undocumented & untested by default and may cause unexpected behavior if used, unless the API actually supports conditions. We should only add those fields in cases where we believe that conditions are supported. Currently this is indicated by the presence of
iam_policy.iam_conditions_request_type
- we could potentially consider adding an explicit indicator of supported vs not.This would be a breaking change because it would remove fields from the resources.
References
#18215 (comment)
The text was updated successfully, but these errors were encountered: