"Instances" are awkward

Bug #1246104 reported by Jort
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
upstart
New
Undecided
Unassigned

Bug Description

This is a feature request, rather than a bug; I started writing this as a blueprint, but got lost.

I have noticed that, in the cookbook, in pretty much ever case where the "instance" clause is used, a separate job, a task, is used to start the right instances. It would seem reasonable to me to add a new clause, to keep the instance together. a "no-instance-specified-start" and "no-instance-specified-stop" clause (to be renamed to something sensible). This means that these are kept together, making it easier to find. It also means that instance-based jobs can "start on/stop on".

I realise that things work 100% as they are now, and you have about a 119 more important things to do.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.