-
Notifications
You must be signed in to change notification settings - Fork 116
feat(status): display pinned deployments #1285
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
Conversation
12f9499
to
82f0a72
Compare
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.
Thanks so much for working on this!!
8ab8d31
to
9a8fee3
Compare
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.
Sorry about the delay in review, looks good to me!
One minor thing right now is you'll need to rebase and update the new spec fixture because there's a new required stateroot
field.
BTW I tried to do this myself to save the review -> wait -> edit -> push -> wait -> merge cycle, but I think you have "allow edits from maintainers" disabled on your PRs. |
Thanks! Will rebase shortly and re-test.
No worries at all! I'm much more excited for the Composefs backend and factory reset work than being able to see pinned deployments 😆
I've not explicitly disabled anything. Or at least, not on purpose. |
Part of bootc-dev#904 Displays pinned deployments as part of "bootc status". Includes unit tests to ensure correct parsing of the pinned deployments, and that they are displayed in human readable formats correctly. Signed-off-by: Robert Sturla <[email protected]>
Rebased onto the latest main branch.
It all still functions locally as before.
I'd much rather you be nitpicky when reviewing this PR than create follow ups. This is how I'll improve. |
Part of #904
Displays pinned deployments as part of "bootc status".
Includes unit tests to ensure correct parsing of the
pinned deployments, and that they are displayed in
human readable formats correctly.
Please find below how they look in both human and machine readable formats.
When the staged, booted or rollback deployments are pinned, the information is not duplicated in the outputs.
Please let me know if this output format is alright, or if you'd prefer some changes.
Human readable:
YAML: