New api route to force export from postgres to mongo #402
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
antoineludeau
requested review from
nkokla,
vinsag,
jbouhadoun,
IGNFBourcier and
FLoreauIGN
nkokla
reviewed
May 3, 2024
nkokla
approved these changes
Jun 5, 2024
antoineludeau
force-pushed
the
antoineludeau/new-route-to-force-export-from-postgres-to-mongo
branch
from
c2c7efc to
d7f398f
Compare
antoineludeau
deleted the
antoineludeau/new-route-to-force-export-from-postgres-to-mongo
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.
Context
In order to force an update from postgres to mongo, we need a new API route
Enhancement
This PR adds a new route :
export-to-exploitation-db/districtsthat takes a body with the list of district IDs in an array :{districtIDs:["","",...]}. This route adds a job in the "export-to-exploitation-db" queue for each district ID requested.