MS: Update MSOutput record schema #9901
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
|
Jenkins results:
|
|
Jenkins results:
|
|
Jenkins results:
|
few bugfixes for MSOutput change Consumer pipeline; fixed isRelval setting make sure TransferStatus gets validated before updating it
|
Jenkins results:
|
|
This has been tested enough and it's good to go. |
This was referenced Sep 11, 2020
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.
Fixes #9797
Fixes #9610
Status
tested
Description
This pull request reflects all the discussions we had over the last few months on which mongodb record schema we should use for MSOutput documents.
In short, changes are:
isTakenandisTakenByTransferStatusvalue, onlypending | doneis allowedpendingstatusIs it backward compatible (if not, which system it affects?)
no, schema changes. It is not in production though, so we can drop the mongo database.
Related PRs
none
External dependencies / deployment changes
none