ee3760e1ba
The previous version covered too few use cases, more specifically a single subscription. That is of course not the case for many hosts, so osbuild needs to understand subscriptions. When running org.osbuild.curl source, read the /etc/yum.repos.d/redhat.repo file and load the system subscriptions from there. While processing each url, guess which subscription is tied to the url and use the CA certificate, client certificate, and client key associated with this subscription. It must be done this way because the depsolving and fetching of RPMs may be performed on different hosts and the subscription credentials are different in such case. More detailed description of why this approach was chosen is available in osbuild-composer git: https://github.com/osbuild/osbuild-composer/pull/1405 |
||
|---|---|---|
| .. | ||
| data | ||
| mod | ||
| pipelines | ||
| run | ||
| src | ||
| .gitignore | ||
| __init__.py | ||
| initrd.py | ||
| test.py | ||