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.
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
[nexus] Remove zones on expunged disks #5599
[nexus] Remove zones on expunged disks #5599
Changes from all commits
46f2be6
138a116
5229eff
cf201dc
ad2d33a
5ba3a5c
309ab31
75c689b
b1580f6
2e887c5
7053eb5
09f4162
9e1e18a
ffbdb3b
1f082ed
0ce9154
65d0cf3
e80756b
e62259d
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Yeah this is exactly the comment handling I was talking about in #5493 -- thanks for doing this!
I think I might consider doing this at a higher level. Instead of storing a list of comments in the
BlueprintBuilder
, store a log of operations. Then, while converting aBlueprintBuilder
into aBlueprint
, turn the log of operations into comments (after possibly doing some merging of operations). That would separate out the data layer from the presentation layer -- and you can test against this.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.
I'm interested in this proposal, but it seems like it might extend a fair bit beyond the scope of this PR. Right now, the
BlueprintBuilder
is modifying structures in-place, rather than having a clear delineation of the "before" + "applied operations" .If I was to implement what you're suggesting, presumably we'd alter the
change_sled_zones
andchange_sled_disks
- rather than mutating in place, we'd need some way to represent operations as "additions, updates, or removals" that are stored separately, and applied when we build the blueprint?(That's my interpretation of your comment at least, am I reading that right?)
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.
Ah so we decided not to do this in #5493. Instead, what we can do is to both apply the changes, and store a structured log of the changes.
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.
I've attempted to resolve this in #5834, or at least start this, with an operation log. It is currently being stringified when the blueprint is built, but it could remain a stronger type eventually, if that would be useful.