Split cartographer into two containers
#1387
Merged
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
rhlsthrm
approved these changes
Jun 9, 2022
|
Pending TF ops. |
sanchaymittal
deleted the
1386-as-a-user-transfer-and-router-data-should-be-available
branch
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.
Description
Transfer and router state data should be reliably stored in catographer DB
Type of change
High-level change(s) description - from the user's perspective
mprove resiliency by running routers and transfers state update in separate docker containers.
Separate DB migration into separate step during deployment.
Related Issue(s)
Fixes
#1386
Related pull request(s)