-
-
Notifications
You must be signed in to change notification settings - Fork 105
Issue-122/Values expect list of strings vs string #123
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
Conversation
@carterdanko-dw this looks solid and we're happy to accept the patch -- one question before we do: Can you do some research on if this is due to an AWS provider versioning change? As in in 4.x AWS Provider, this was fine and was working well for folks, but in 5.x AWS provider they're now enforcing this be a list? I assume that is why this was the way it was before... and I want to confirm as we may want to change the provider pins to accommodate. Appreciate it -- Thanks! |
/terratest |
Ahh yep let me take a look and compare |
Tried to modify our versions, Previously we had
|
Just checking back @Gowiem but it looks like at least from my local testing, things were still failing? Could be a PEBCAK though as well with the 4.x version not working and this is just a 5.x issue. From the docs on the provider, there is no real change related to this, but I haven't looked through the release notes or anything explicitly. |
/terratest |
These changes were released in v1.4.4. |
what
Updating the sqs iam permissions, as the values expects to be a list of strings vs just the single string arn that is the output of the module.
why
https://registry.terraform.io/providers/hashicorp/aws/latest/docs/data-sources/iam_policy_document#condition-1 expects to be a list of strings, vs just the single string arn of the s3 bucket.
references
Github issue #122