Tomáš Hozza 7437770352 composer: don't create RepoRegistry using reporegistry.New() ... The `reporegistry.New()` has been enhanced to return an error, in case there were no repositories loaded. This was to fix the situation in many unit tests, which were previously not loading any repositories and silently not running any tests. This however broke our SaaS deployment, where we actually do not configure any repositories on the filesystem. As a result, osbuild-composer started to fail on it. Workaround this situation in osbuild-composer by reverting to the old behavior by loading the repo configs separately and then using the loaded repos (which could be empty map) to initialize the RepoRegistry. Signed-off-by: Tomáš Hozza <thozza@redhat.com>		2024-09-23 18:51:39 +02:00
..
testdata	osbuild-composer/config: support specifying distro aliases	2024-01-26 11:32:34 +01:00
composer.go	composer: don't create RepoRegistry using reporegistry.New()	2024-09-23 18:51:39 +02:00
config.go	logrus: add deployment channel as field to the logs	2024-08-07 12:32:57 +02:00
config_test.go	Config: don't override undefined keys when loading from ENV	2024-07-17 11:02:41 +02:00
main.go	splunk_logger: move environment hook to splunk_logger pt2	2024-08-28 16:41:07 +02:00