The iam_policy input introduced in v1.0.0 has been changed from type object to type list(object). This allows multiple policy objects to be provided, but more importantly, allows no input or allows the iam_policy input to be used along with the deprecated iam_policy_statements input.
Reversion of Breaking Change
In v1.0.0, the iam_policy_statements input was deprecated, but it was also converted from type any to type map(object), which was how it was documented. However, it was, in practice, allowed to be a list or a map, and many users were supplying lists. This made it an unintentional breaking change for those users.
In this release, iam_policy_statements (while still deprecated) is reverted to type any and accepts both a map and a list.
what
Revert iam_policy_statements back to type = any
Convert iam_policy input to list
Update documentation
why
Preserve backward compatibility with pre v1.0 module
Enable all inputs to be used in any combination
Reflect changes to usage, remove leftovers from initial template
Nuru
commented
1 year ago
Breaking Change
The
iam_policyinput introduced in v1.0.0 has been changed from typeobjectto typelist(object). This allows multiple policy objects to be provided, but more importantly, allows no input or allows theiam_policyinput to be used along with the deprecatediam_policy_statementsinput.Reversion of Breaking Change
In v1.0.0, the
iam_policy_statementsinput was deprecated, but it was also converted from typeanyto typemap(object), which was how it was documented. However, it was, in practice, allowed to be a list or a map, and many users were supplying lists. This made it an unintentional breaking change for those users.In this release,
iam_policy_statements(while still deprecated) is reverted to typeanyand accepts both a map and a list.what
iam_policy_statementsback totype = anyiam_policyinput tolistwhy
references