[8/n] [reconfigurator] add target release generation to blueprint #8199
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.
As described in RFD 556, we need this field as a backstop against Nexus overriding a freshly-conducted mupdate.
There is small semantic change here compared to RFD 556, though not one of much consequence:
This has two advantages:
target_release_minimum_generation
no longer needs to be anOption<Generation>
; it can be aGeneration
instead. That's because we always insert a generation 1 in the target_release table as "unspecified", meaning to use the install dataset. So setting this field to generation 1 just means "use the install dataset".