Plan zone updates for target release #8024
Draft
Conversation
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
plotnick
force-pushed
the
plan-target-release
branch
2 times, most recently
from
0f8fcab to
0b66d64
Compare
plotnick
force-pushed
the
plan-target-release
branch
from
0b66d64 to
08c316d
Compare
plotnick
force-pushed
the
plan-target-release
branch
from
8019b67 to
b254f32
Compare
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.
Plumb the TUF repo representing the current
target_releasethrough the policy and planner. Update one zone at a time to the control-plane artifacts in that repo.TODO:
The current test asserts the opposite of what should happen with, e.g., a new Nexus zone.