ausil / fedora-coreos-config

Base configuration for Fedora CoreOS

Fedora CoreOS Config

Base manifest configuration for Fedora CoreOS.

Use https://github.com/coreos/coreos-assembler to build it.

Discussions in https://discussion.fedoraproject.org/c/server/coreos and https://github.com/coreos/fedora-coreos-tracker.

About this repo

There is one branch for each stream. The default branch is testing-devel, on which all development happens. See the design and tooling docs for more information about streams.

All file changes in testing-devel are propagated to other branches (to bodhi-updates through config-bot, and to testing through usual promotion), with the following exceptions:

• manifest.yaml: contains the stream "identity", such as the ref, additional commit metadata, and yum input repos.
• lockfiles (manifest-lock.* files): lockfiles are imported from bodhi-updates to testing-devel. Overrides (manifest-lock.overrides.*) are manually curated.

Adding packages to the OS

Since testing-devel is directly promoted to testing, it must always be in a known state. The way we enforce this is by requiring all packages to have a corresponding entry in the lockfile.

Therefore, to add new packages to the OS, one must also add the corresponding entries in the lockfiles:

• for packages which should follow Bodhi updates, place them in manifest-lock.$basearch.json
• for packages which should remain pinned, place them in manifest-lock.overrides.$basearch.json

There will be better tooling to come to enable this, though one easy way to do this is for now:

• add packages to the correct YAML manifest
• run cosa fetch --update-lockfile
• commit only the new package entries