Allow configuring IAM deprecation, batching, and timeouts as part of the iam_policy block #23048
Labels
mmv1-generator
Provider-wide changes to resource templates or other generator changes
size/m
technical-debt
Milestone
What kind of contribution is this issue about?
MMv1-based resource
Details
Currently, we don't support setting timeouts for IAM resources at all, and we only support deprecating IAM resources or enabling batching for handwritten resources that pass helper functions as part of being registered with the provider.
We should support configuring all three via the MMv1
iam_policy
block.(In my opinion, we should also get rid of the
settings
function mechanism in favor of something easier to understand, but that's not strictly a blocker.)References
No response
The text was updated successfully, but these errors were encountered: