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
support for pebble service manager #3207
Comments
No problem about adding a plugin - we just need a short list of what config files and/or command collections you'd like to see in it. Also if there is any helpful information that can be programmatically collated from either of those sources, we now have support for that in plugins as well. One clarification for me - is pebble an init system in the same vein systemd is? If so, would it make sense to add a runtime abstraction for it so that plugins can be enabled based on the services pebble manages on systems that use it? |
@TurboTurtle I'd be interested in working on this so can you assign me to this issue please? I'm not able to assign myself to it maybe a permissions issue |
Done. |
Closes: sosreport#3207 Resolves: SET-86 Signed-off-by: Arif Ali <arif.ali@canonical.com>
Closes: sosreport#3207 Resolves: SET-86 Signed-off-by: Arif Ali <arif.ali@canonical.com>
Closes: sosreport#3207 Resolves: SET-86 Signed-off-by: Arif Ali <arif.ali@canonical.com>
Closes: sosreport#3207 Resolves: SET-86 Signed-off-by: Arif Ali <arif.ali@canonical.com>
We have some deployments that use https://github.com/canonical/pebble to manage services and it would be helpful if sosreport contained related information in a similar way to the systemd plugin.
The text was updated successfully, but these errors were encountered: