-
Notifications
You must be signed in to change notification settings - Fork 117
go.mod: update osbuild/images to v0.95.0 #4448
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
fe48bb7 to
7f38ffb
Compare
|
Bunch of failures here and I suspect I missed a test config that should have the new option enabled. Looking at the journal log from one of the API-module-hotfixes tests, I see that But, if I'm reading the test setup correctly:
🤔 |
Oh, I see... |
7f38ffb to
afc2c9b
Compare
thozza
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Amazing, thanks!
afc2c9b to
78cf7da
Compare
|
Sorry, missed a couple of more test configs. -_- |
osbuild/images added an error type that's returned when the reporegistry loader doesn't find any repository configurations to load [1]. This lets callers decide whether to stop or continue execution based on whether repository configurations are required. A new top-level configuration option is added for osbuild-composer that makes it possible to start the service without having static rpm repositories configured. This is useful in certain (SaaS) modes where build requests specify their own repository configurations.
If weldr tries to initialise when there are no repositories set and ignore_missing_repos is enabled, return with an error.
78cf7da to
02b3c02
Compare
thozza
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
All green! |
This is a small update that only includes one PR from osbuild/images: osbuild/images#946
The second and third commits change the behaviour of osbuild-composer's startup when no repositories are configured.
Weldr (running on-prem) requires local repository configurations, while the API (SaaS) doesn't. However, at the time during startup when reporegistry.LoadAllRepositories() is called, it is still not known whether the Weldr API will be initialised.
Since lack of repository configurations is no longer a stop condition for osbuild-composer's startup, the Weldr API will now return with an error when no repositories are configured during its initialisation.