I'd like this as well. The only way to do things like this today is to wrap the services that require configs (or databases, whatever) in a script and make that script the daemon. It'd be great if that was an optional step (e.g. if I wanted to verify a config before launching it, as Mark mentioned) and the heavy lifting of generating things needed in order to run was handled in a dedicated place. Having wrappers for all my daemons makes my snap difficult to navigate and maintain.
I'd like this as well. The only way to do things like this today is to wrap the services that require configs (or databases, whatever) in a script and make that script the daemon. It'd be great if that was an optional step (e.g. if I wanted to verify a config before launching it, as Mark mentioned) and the heavy lifting of generating things needed in order to run was handled in a dedicated place. Having wrappers for all my daemons makes my snap difficult to navigate and maintain.