Enable ordering of services provided by a snap
Bug #1609757 reported by
Dan Watkins
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Snappy |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
An upstream for a piece of software I'm looking at snapping provide two systemd unit files. One of them is a oneshot which does some configuration of the booted system, and the other is a simple daemon which relies on some of the configuration performed by the oneshot.
snapcraft/snapd currently have the primitives for me to express each of these services individually, but I don't have any way of expressing the order in which these services should be executed. I would like to be able to do something like::
apps:
system-
command: ...
daemon: oneshot
long-
command: ...
daemon: simple
run-after: system-config
and have snapd do the right thing.
| tags: | added: cpc |
Revision history for this message
| John Lenton (chipaca) wrote | #1 |
| Changed in snappy: | |
| status: | New → Fix Released |
To post a comment you must log in.
in-snap services can be ordered by specifying before/after as specified in https:/