Implement an Arguments Key Handling for Entry Points Defined in snap-openstack.yaml
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
snap.openstack |
Triaged
|
High
|
Unassigned |
Bug Description
Right now it is only possible to pass additional arguments to an app via a top-level snapcraft.yaml file, for example, ceilometer's agent-central service uses ceilometer-polling script and passes --polling-
https:/
agent-central:
command: snap-openstack ceilometer-polling --polling-
It seems to be cleaner to do it in the snap/snap-
1) like this https:/
2) or via key-value pairs:
arguments:
polling-
The code in question is here https:/
we just need to add a handler for the arguments key.
While we could get away with specifying the arguments in snapcraft.yaml, I agree that it would be cleaner to specify additional arguments in snap-openstack. yaml, alongside other args that are currently passed to the daemon (ie. log files, config files).