Added district config in export to exploitation db #509
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 correctly activate the certificate for the district that have activated it, we need to have more information in our exploitation db (mongo), coming from our main db (postgresql).
Enhancement
this PR adds :
config
on all items transferred from our main db (postgresql) to our exploitation DB (mongodb) : address, common toponym and district in ourwithBanId
on all items transferred from our main db (postgresql) to our exploitation DB (mongodb) : address, common toponym (it was already exported on district items).This PR also adds the config district in the field returned by the
lookup