This looks sane, but how do we push it to a registry after the OCI artifact is built?

There's a couple of tools rel-eng uses

Is this the one we're actually using?

We may also need some of the config from the other ostree build for signing and related pieces. I suspect we start with this and get it running and then see what we're missing.

Updated the url and filename to use ours rather than upstream, to help us test and make changes quickly if needed.

Updated the url and filename to use ours rather than upstream, to help us test and make changes quickly if needed.

I worry we are going to run into the problem of keeping up with changes in https://github.com/CentOS/centos-bootc by using our own manifest file in this repo.

Could we just get https://github.com/CentOS/centos-bootc/pull/480 merged and use that?

I worry we are going to run into the problem of keeping up with changes in https://github.com/CentOS/centos-bootc by using our own manifest file in this repo.

Could we just get https://github.com/CentOS/centos-bootc/pull/480 merged and use that?

I think we are too close to the wire for F-40 now, we need a level of sanity and we can revisit it post GA, I would sooner have some level of control where we can pull things in to lessen the effect of the firehose and have something vaguely stable.