Update Terraform cloudposse/iam-policy/aws to v2 #289
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.
This PR contains the following updates:
0.4.0
->2.0.1
Release Notes
cloudposse/terraform-aws-iam-policy (cloudposse/iam-policy/aws)
v2.0.1
Compare Source
🐛 Bug Fixes
Remove problematic conditional @Nuru (#31)
what
why
local.deprecated_statements_values
can be a tuple, and Terraform does not have a concept of an empty or null tuple to use as an alternative in a conditional, so you can get an error like:references
v2.0.0
: Revert breaking change in 1.0, add new breaking changeCompare Source
Revert deprecated input to type "any" @Nuru (#30)
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
v1.0.1
Compare Source
🚀 Enhancements
fix: support JSON inputs for policy document when IAM policy/statements are not set as Terraform objects @gberenice (#28)
what
why
var.iam_policy
andvar.iam_policy_statments
may remain unset. The precondition fails in this case:references
v1.0.0
: Accept policy as fully defined objectCompare Source
Breaking Change (updated)
The
iam_policy_statements
input has been converted fromtype = any
totype = map(object)
, as the documented (though not enforced by Terraform) input type was a map of IAM Policy Statement objects. While the object type was backward compatible, in practice, the input accepted a list as well as a map, and the majority of (later) surveyed users of this module were providing lists. This release broke those clients. Version 2.0.0 of this module reverts the type change and restores backward compatibility with pre-1.0.0 versions of this module.The new
iam_policy
input is of typeobject
. In v2.0.0, this is changed to typelist(object)
.What's Changed
New Contributors
Full Changelog: cloudposse/terraform-aws-iam-policy@0.4.0...1.0.0
v0.5.0
Compare Source
Add conditions @nitrocode (#19)
what
why
references
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.