[WIP] Add scripts to create iso using bootc-image-builder

[praveenkumar]

Which issue(s) this PR addresses:

Closes #

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: praveenkumar
Once this PR has been reviewed and has the lgtm label, please assign pacevedom for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ggiguash]

@praveenkumar ,
I'm not sure we want to support these scripts in the dev repository. I believe, we should instead update the https://github.com/openshift/microshift/blob/main/docs/contributor/image_mode.md documentation and refer users to it when necessary.

[praveenkumar]

@praveenkumar , I'm not sure we want to support these scripts in the dev repository. I believe, we should instead update the https://github.com/openshift/microshift/blob/main/docs/contributor/image_mode.md documentation and refer users to it when necessary.

@ggiguash you mean those script should be part of docs/config instead as part of scripts directory? I kind of have a hidden agenda around those scripts to be part of microshift (location doesn't matter) to consume directly it to my other project (like cloning it and execute). BTW we can even have e2e test for BIB + deploying final iso/qcow2 generated using those if this we want in future or is it already tested somewhere else?

[ggiguash]

you mean those script should be part of docs/config instead as part of scripts directory?

Such scripts are intended for devenv setup and we have previous experience with build.sh I would not want to repeat. Users took it as a base for their procedures, but it was very contextual and not correct for all the cases.

For what I'd like to see is an augmentation of the image_mode.md page with this w/f, using the same style - instructions rather than a full script.

[praveenkumar]

you mean those script should be part of docs/config instead as part of scripts directory?

Such scripts are intended for devenv setup and we have previous experience with build.sh I would not want to repeat. Users took it as a base for their procedures, but it was very contextual and not correct for all the cases.

For what I'd like to see is an augmentation of the image_mode.md page with this w/f, using the same style - instructions rather than a full script.

@ggiguash Understood, will move the script to our project and update the image mode doc with BIB info in this PR.