Post deployment commands
Bug #1270174 reported by
Charles Butler
This bug affects 3 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Amulet |
Fix Released
|
High
|
Marco Ceppi | ||
Bug Description
Post deployment, amulet needs to proxy juju commands for removing relations, destroying services, exposing, and adding/removing units
| description: | updated |
Revision history for this message
| Marco Ceppi (marcoceppi) wrote | #1 |
| Changed in amulet: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| assignee: | nobody → Marco Ceppi (marcoceppi) |
| milestone: | none → 1.2.0 |
Revision history for this message
| Marco Ceppi (marcoceppi) wrote | #2 |
| Changed in amulet: | |
| milestone: | 1.2.0 → 1.2.1 |
| Changed in amulet: | |
| milestone: | 1.2.1 → 1.2.2 |
| Changed in amulet: | |
| milestone: | 1.2.2 → 1.3.0 |
| Changed in amulet: | |
| status: | Triaged → In Progress |
| Changed in amulet: | |
| status: | In Progress → Fix Committed |
| Changed in amulet: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
This should be transparent to the user.
// These create deployer file
d.add('mysql')
d.configure(
d.setup()
// This will use juju set mysql from command line
d.configure(
d.add_unit('mysql')