Generate konflux lockfiles during import
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
ok. I've review the first few commits but the last two I think I'm going to need to clear my head for.
I'm thinking about this in totality with how all the other pieces fit. Let me get back to it after a few meetings clear out of the way.
@dustymabe @jbtrystram and I discussed about this PR on video call today. See below the summarize:
- use the rpm-ostree manifest as source of truth in the config repository e.g: fedora-coreos-config for Fedora, and generate the
rpms.lock.yamlfile on-the-fly in Konflux pipeline i.e within the prepare-build-context Tekton task. We'd stop committingrpms.lock.yamlin repo. This would simplify the way we handle Konflux lockfile until the integration of https://github.com/rpm-software-management/dnf5/issues/2370 in Konflux/Hermeto. - break down this PR into multiple ones to keep changes we want to merge, and closing this one.
break down this PR into multiple ones to keep changes we want to merge
https://github.com/coreos/coreos-assembler/pull/4398 and https://github.com/coreos/coreos-assembler/pull/4399