Update docs to reference image builder CLI #186
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
melcorr
force-pushed
the
ibcli-doc-updates
branch
from
1f1a310 to
3aec955
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Recently I walked through all the image-builder workflows.
Because the docs had the composer-cli steps, I used this and thought that image-builder CLI wasn't available.
Then Justin Sherrill told me I could actually use image-builder CLI. From my perspective using image-builder CLI was an immediate, positive improvement to the workflow.
I marked this as draft because I am worried about this section:
https://github.com/osbuild/osbuild.github.io/compare/main...melcorr:osbuild.github.io:ibcli-doc-updates?expand=1#diff-69e48e37a22a2d556c2f023b7f62fbe1ed7ae365f0484fbecc7810dd5e715e42R58
I was walking through the steps on a Fedora 43 VM in UTM on my Mac. I want to provide steps that I've validated but I cannot validate the boot of an x86_64 image. Can someone tell me if I need to update this step or is it all good?
I also wonder should I keep the original compose-cli docs somewhere until the web UI is updated?
Let me know.