Skip to content
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

Open
wants to merge 9 commits into
base: main
Choose a base branch
from

Conversation

nnsense
Copy link

@nnsense nnsense commented Aug 27, 2024

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

@nnsense nnsense requested review from a team as code owners August 27, 2024 16:15
@nnsense nnsense requested review from Gowiem and nitrocode August 27, 2024 16:15
@nnsense nnsense changed the title Implementing the Implementing the aws_dynamodb_resource_policy resource to allow a user to set the table or stream's resource policy. Aug 27, 2024
@mergify mergify bot added the triage Needs triage label Aug 27, 2024
@GabisCampana
Copy link

@milldr

@GabisCampana
Copy link

@Benbentwo

variables.tf Show resolved Hide resolved
@milldr
Copy link
Member

milldr commented Aug 28, 2024

/terratest

@nnsense
Copy link
Author

nnsense commented Aug 28, 2024

Uhm.. apparently the tests are failing because there are tables with the same names deployed.

Copy link

mergify bot commented Sep 19, 2024

💥 This pull request now has conflicts. Could you fix it @nnsense? 🙏

@mergify mergify bot added the conflict This PR has conflicts label Sep 19, 2024
@mergify mergify bot removed the conflict This PR has conflicts label Sep 25, 2024
@nnsense
Copy link
Author

nnsense commented Sep 25, 2024

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 :)

@Gowiem Gowiem added the minor New features that do not break anything label Sep 25, 2024
@Gowiem
Copy link
Member

Gowiem commented Sep 25, 2024

/terratest

@nnsense
Copy link
Author

nnsense commented Sep 25, 2024

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?

Error: creating AWS DynamoDB Table (eg-test-second): operation error DynamoDB: CreateTable, https response error StatusCode: 400, RequestID: 80SJ66BV4QO342D4VUTSEERMJJVV4KQNSO5AEMVJF66Q9ASUAAJG, ResourceInUseException: Table already exists: eg-test-second

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
minor New features that do not break anything triage Needs triage
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants