-
Notifications
You must be signed in to change notification settings - Fork 63
Remove ability to generate a Blueprint from an inventory collection #5583
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
0727514
wip - removing blueprint from collection
jgallagher 4cb403d
wip - removing blueprint from collection
jgallagher 0fc4c6d
wip - removing blueprint from collection
jgallagher e41b2a2
remove build_initial_from_collection from DNS tests
jgallagher 7d6784b
update nexus internal openapi
jgallagher 46bd51a
fix broken rustdoc link
jgallagher 0dfbfdd
Merge remote-tracking branch 'origin/main' into john/remove-blueprint…
jgallagher 152cfac
remove stray dbg!
jgallagher da9d7e4
rustdoc fixes
jgallagher 692d55a
Merge branch 'main' into john/remove-blueprint-from-collection
jgallagher File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This assertion change is, I believe, a fix for a test that was passing incorrectly.
blueprint_disksis aBTreeMap<SledUuid, PhysicalDisksConfig>, which meansblueprint_disks.len()reported "for how many sleds do we have aPhysicalDisksConfig?", not "how many disks are in the blueprint" as the check seemed to mean. I think this was passing purely by coincidence:blueprint1.blueprint_diskswas empty, because a blueprint created from an inventory collection didn't populate it at allnew_sled_zpoolswas 4, because we added 4 disksblueprint2.blueprint_disks.len()was 4, because there are 4 sleds in blueprint2, and going through the builder populatesblueprint_disksso we were previously passing because
0 + 4 == 4, even though the units of these values made the comparison nonsensical.