-
Notifications
You must be signed in to change notification settings - Fork 53
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
Composer service (HMS-5455) #2847
Conversation
Codecov ReportAttention: Patch coverage is
@@ Coverage Diff @@
## main #2847 +/- ##
==========================================
- Coverage 83.04% 82.73% -0.31%
==========================================
Files 200 202 +2
Lines 22802 22887 +85
Branches 2256 2258 +2
==========================================
Hits 18936 18936
- Misses 3844 3927 +83
- Partials 22 24 +2
Continue to review full report in Codecov by Sentry.
|
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.
Nice! One nitpick, also we should probably change the name of the osbuild-composer socket definition lol, but that's obviously for composer.
Add a component to display when the osbuild-composer socket is not running. We could potentially try start the socket in the future when clicking the button, rather than re-directing to the cockpit services plugin.
Add a custom hook to check to see if the osbuild-composer.socket is enabled & running.
Render the nont ready component when the osbuild-composer.socket is not running.
Add a secondary button that takes the user to the `osbuild-composer.socket` services file inside the cockpit services plugin.
7cd41b7
to
e017587
Compare
osbuild-composer.socket
osbuild-composer.socket
if the unit is disabled/not activeScreen.Recording.2025-02-04.at.16.02.12.mov
/jira-epic COMPOSER-2411
JIRA: HMS-5455