Take code branches as configuration arguments
Bug #1085915 reported by
Evan
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ubuntu Error Tracker deployment |
Fix Released
|
Medium
|
Unassigned | ||
Bug Description
We should be able to set code branches as part of the configuration data for each charm. This way we can test changes easily by pointing the charms at our local branches for daisy, errors, etc. This should respect the config-changed event, so we can do this to an already-deployed infrastructure.
| Changed in error-tracker-deployment: | |
| importance: | Undecided → Medium |
| status: | New → Triaged |
| Changed in error-tracker-deployment: | |
| status: | Triaged → Fix Released |
To post a comment you must log in.
We use the upgrade-charm facility and code tarballs instead now.