provider/aws: Fix data.aws_iam_policy_document #7611
Conversation
| @@ -71,14 +72,15 @@ valid to use literal JSON strings within your configuration, or to use the | |||
|
|
|||
| The following arguments are supported: | |||
|
|
|||
| * `id` (Optional) - An ID for the policy document. | |||
| * `version` (Optional) - An policy version. Defaults to `2012-10-17`. | |||
There was a problem hiding this comment.
We should probably document that if you set this to 2008-10-17 then you can't use policy variables.
(Though I don't know why anyone would set this to anything other than what it defaults to anyway.)
There was a problem hiding this comment.
@apparentlymart the reason I had was for existing ones what shouldn't be modified (for whatever reason) - happy to point out in the docs that the default should be fine for almost all use cases though
There was a problem hiding this comment.
Actually having researched this I am in agreement @apparentlymart, and will remove version again.
We cannot use the "id" field to represent policy ID, because it is used internally by Terraform. Also change the "id" field within a statement to "sid" for consistency with the generated JSON.
jen20
force-pushed
the
b-iam-policy-document-fixes
branch
from
8cb9970
to
28438da
Compare
|
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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
ghost
locked and limited conversation to collaborators
Adds ID and Version support to policy documents.
Fixes #7499.