systemdUnitFilePlugin
systemdUnitFilePlugin copied to clipboard
Probably Implement Different Languages
There are several types of Units, e.g., Service, Timer, etc... And the plugin was originally structured around this convention. As we have expanded into other parts of systemd however there is now two levels of abstraction, not every file we support is now a Unit. We have supported this using FileClass today but the main limitation about this approach is that it's entirely our our convention, and in some cases we we can't make a determination.
For instance
- Using language injections (like we do in tests), we don't really know the file class, and so can't really do anything.
- It's likely true no one else but me cares about this.
- Override files, for instance you can have .conf files where the directory name is the unit name (e.g.,
.service.d/10-override.conf/, or say a config file for a network. You can search these pages for override: https://www.freedesktop.org/software/systemd/man/latest/systemd.unit.html or https://www.freedesktop.org/software/systemd/man/latest/systemd.network.html
Anyway we probably want to split things up into different languages.