Revert deprecated input to type "any" #30
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Breaking Change
The
iam_policy
input introduced in v1.0.0 has been changed from typeobject
to typelist(object)
. This allows multiple policy objects to be provided, but more importantly, allows no input or allows theiam_policy
input to be used along with the deprecatediam_policy_statements
input.Reversion of Breaking Change
In v1.0.0, the
iam_policy_statements
input was deprecated, but it was also converted from typeany
to 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 typeany
and accepts both a map and a list.what
iam_policy_statements
back totype = any
iam_policy
input tolist
why
references