[1/n] [reconfigurator-planning] move determination of add/update zones into a separate method#8920
Merged
Conversation
Created using spr 1.3.6-beta.1
jgallagher
approved these changes
Aug 27, 2025
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I'd like to determine condition 4 of whether to perform updates (all deployment units are at known versions) by looking at the blueprint after noop conversions have been applied. We could either try and guess what would happen by looking at the noop info, or just move this determination to after noop updates have been applied.
Also make the planning report store the reasons zone adds and updates are blocked, and print them as part of the planning report.
There are no behavior changes in this PR.