Provide an option to specify creation of a new instance upon deployment
Bug #993288 reported by
Robert Ayres
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pyjuju |
Triaged
|
Low
|
Unassigned |
Bug Description
Currently, if you destroy a deployed service, the machine instance is re-used when deploying a new charm. It'd be great if you could specify via a flag, maybe '--new-instance', that a new instance should be created and used for this deployment. This is particularly useful if you destroy a service but want to keep the instance dormant in the background for further tasks, e.g. data retrieval.
juju 0.5+bzr531-0ubuntu1
Changed in juju: | |
status: | Confirmed → Triaged |
Changed in juju: | |
importance: | Medium → Low |
To post a comment you must log in.
Great idea Robert. I think the workaround right now is just to deploy something non-destructive to any instances you want to keep around, like a "null" charm or something.