-
Notifications
You must be signed in to change notification settings - Fork 9.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clarify that overriding policy document statements can be added to current document if sid
does not match
#17468
Clarify that overriding policy document statements can be added to current document if sid
does not match
#17468
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Welcome @aperiodic 👋
It looks like this is your first Pull Request submission to the Terraform AWS Provider! If you haven’t already done so please make sure you have checked out our CONTRIBUTING guide and FAQ to make sure your contribution is adhering to best practice and has all the necessary elements in place for a successful approval.
Also take a look at our FAQ which details how we prioritize Pull Requests for inclusion.
Thanks again, and welcome to the community! 😃
…rrent document if `sid` does not match In the description of `iam_policy_document` data source's `override_json` argument, state specifically that any statements in the override document that have `sid`s that do _not_ match a statement in the current document will be added to the current document, instead of ignored. Before this change, there was no description of how non-matching statements in the `override_json` were used, so the behavior was unclear: the opposite and incorrect conclusion that these statements were ignored was equally consistent with the documentation. This behavior is covered by an acceptance test, so from the coverage I'm inferring that this behavior is both intended and supported.
fcde276
to
de5c76c
Compare
de5c76c
to
755ac6f
Compare
@aperiodic Thank you for noticing this hole in the documentation and taking the initiative to fill it! 🎉 This builds on a fairly extensive overhaul of the |
This has been released in version 3.28.0 of the Terraform AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template for triage. Thanks! |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
In the description of
iam_policy_document
data source'soverride_json
argument, state specifically that any statements in theoverride document that have
sid
s that do not match a statement inthe current document will be added to the current document, instead of
ignored. Before this change, there was no description of how
non-matching statements in the
override_json
were used, so thebehavior was unclear: the opposite and incorrect conclusion that these
statements were ignored was equally consistent with the documentation.
This behavior is covered by an acceptance test, so from the coverage I'm
inferring that this behavior is both intended and supported.
Community Note
I am omitting the output from acceptance testing, because this is a documentation-only change.