Mirrors/network
1
0
Fork 0
mirror of https://github.com/linux-system-roles/network.git synced 2026-01-23 02:15:17 +00:00
Code Issues Projects Releases Wiki Activity
network/README-ostree.md
Rich Megginson c22e1fcd46 ci: use ANSIBLE_INJECT_FACT_VARS=false by default for testing 
Ansible 2.20 has deprecated the use of Ansible facts as variables.  For
example, `ansible_distribution` is now deprecated in favor of
`ansible_facts["distribution"]`.  This is due to making the default
setting `INJECT_FACTS_AS_VARS=false`.  For now, this will create WARNING
messages, but in Ansible 2.24 it will be an error.

In order to ensure that commits and PRs conform to this, use
ANSIBLE_INJECT_FACT_VARS=false by default in our CI testing.

Update README-ostree.md if needed.

See https://docs.ansible.com/projects/ansible/latest/porting_guides/porting_guide_core_2.20.html#inject-facts-as-vars

Signed-off-by: Rich Megginson <rmeggins@redhat.com>
2026-01-13 10:29:37 -05:00

1.9 KiB
Raw Blame History

rpm-ostree

The role supports running on rpm-ostree systems. The primary issue is that the /usr filesystem is read-only, and the role cannot install packages. Instead, it will just verify that the necessary packages and any other /usr files are pre-installed. The role will change the package manager to one that is compatible with rpm-ostree systems.

Building

To build an ostree image for a particular operating system distribution and version, use the script .ostree/get_ostree_data.sh to get the list of packages. If the role uses other system roles, then the script will include the packages for the other roles in the list it outputs. The list of packages will be sorted in alphanumeric order.

Usage:

.ostree/get_ostree_data.sh packages runtime DISTRO-VERSION FORMAT

DISTRO-VERSION is in the format that Ansible uses for ansible_facts["distribution"] and ansible_facts["distribution_version"] - for example, Fedora-38, CentOS-8, RedHat-9.4

FORMAT is one of toml, json, yaml, raw

  • toml - each package in a TOML [[packages]] element
[[packages]]
name = "package-a"
version = "*"
[[packages]]
name = "package-b"
version = "*"
...
  • yaml - a YAML list of packages
- package-a
- package-b
...
  • json - a JSON list of packages
["package-a","package-b",...]
  • raw - a plain text list of packages, one per line
package-a
package-b
...

What format you choose depends on which image builder you are using. For example, if you are using something based on osbuild-composer, you will probably want to use the toml output format.