-
-
Notifications
You must be signed in to change notification settings - Fork 110
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
Implementing the aws_dynamodb_resource_policy
resource to allow a user to set the table or stream's resource policy.
#135
base: main
Are you sure you want to change the base?
Conversation
aws_dynamodb_resource_policy
resource to allow a user to set the table or stream's resource policy.
/terratest |
Uhm.. apparently the tests are failing because there are tables with the same names deployed. |
💥 This pull request now has conflicts. Could you fix it @nnsense? 🙏 |
Hi guys, I've resolved the conflict, but time has passed and I don't remember if I needed to do anything else to get this merged, can you advise? Thanks :) |
/terratest |
Hi @Gowiem thanks for running the test, this is still failing for the same reason above, and I don't know what to do about it, the table is deployed only once, or at least it seems so, are those two tables actually still online maybe?
|
what
This minor change is to implement the aws_dynamodb_resource_policy resource, to allow a user to set the table or stream's resource policy. Two more variables are added, one for the table policy, the other for the stream. They are implemented separately (even if the resource is the same) to allow the user to set them as separate objects without adding complexity to terraform.
why
It can be useful, if you're implementing DynamoDB as a trigger for example, to set the right policy allowing that