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

fix(dynamodb): cannot reuse container since table already exists #176

Merged
merged 3 commits into from
Apr 2, 2024

Conversation

eladb
Copy link
Contributor

@eladb eladb commented Apr 2, 2024

Now since the container might be reused across simulator updates, we need to make sure we clean up the table before it's being created.

I've tested this manually because I am not sure how to test this.

Now since the container might be reused across simulator updates, we need to make sure we clean up the table before it's being created.
@eladb eladb requested review from skyrpex and Chriscbr April 2, 2024 21:26
@eladb eladb changed the title fix(dynamodb): service cannot start if table already exists fix(dynamodb): cannot reuse container since table already exists Apr 2, 2024
Copy link

mergify bot commented Apr 2, 2024

Thanks for contributing, @eladb! This PR will now be added to the merge queue, or immediately merged if eladb-patch-1 is up-to-date with main and the queue is empty.

@mergify mergify bot merged commit 3e335d4 into main Apr 2, 2024
6 checks passed
@mergify mergify bot deleted the eladb-patch-1 branch April 2, 2024 23:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants