The changes in this request enable installation supervisor via pip, since the distro packages for supervisor are outdated.
What happens is:
Supervisor is installed via pip
Service configuration files (systemd config for redhat and sysv script for debian) are placed using a template
Supervisor is run through those configuration files
Main benefit is for later supervisor packages to be installed (since the latest versions come from pip)
Some requirements:
If the supervisor::provider is set to 'pip', supervisor::pip_ensure must also be set to a valid ensure value (including version)
Some caveats:
Setting the provider to pip after installing a distro package will permanently use pip after unsetting the provider. Since the default is just an ensure of the supervisor package (which is the same name for both pip and dist packages).
The changes in this request enable installation supervisor via pip, since the distro packages for supervisor are outdated.
What happens is:
Main benefit is for later supervisor packages to be installed (since the latest versions come from pip)
Some requirements:
Some caveats: