Fixing dynamodb local v2.0 change plus creating dynamodb tables at startup #281
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sylviamclaughlin
requested review from
maxneuvians,
gcharest and
wanpengyang
gcharest
approved these changes
Sep 28, 2023
Dive image results for
|
| Image | sre-bot:latest |
| Total Size | 1.66GiB |
| Inefficient Bytes | 44.92MiB |
| Efficiency Percentage | 97.58% |
| Total Layers | 21 |
See the PR run for more details
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary | Résumé
Making the dynamodb creation of the databases work, plus fixing a new change that AWS introduced that the access key's and id can't no longer contain special characters since dynamodb local v2.0. Information regarding the proceeding can be found here: