upgrade hook should get access to previous version numbers of the charm
Bug #766721 reported by
Kapil Thangavelu
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Expired
|
Wishlist
|
Unassigned | ||
juju-core |
Won't Fix
|
Medium
|
Unassigned | ||
pyjuju |
Triaged
|
Low
|
Unassigned |
Bug Description
A suggestion mentioned during the cloud meeting, which was not implemented would be to pass to the upgrade hook which version the upgrade process is starting from. This is needed as sometimes the upgrade process depends on the starting version (example upgrade wordpress 2.9 -> 3.0 might involve a DB schema migration, while 3.0 -> 3.1 might not)
Changed in ensemble: | |
milestone: | none → budapest |
Changed in ensemble: | |
milestone: | budapest → dublin |
Changed in ensemble: | |
milestone: | dublin → none |
summary: |
- upgrade hook should get access to previous and new versions numbers of - the formula + upgrade hook should get access to previous version numbers of the charm |
Changed in juju: | |
importance: | Undecided → Wishlist |
status: | New → Confirmed |
Changed in juju: | |
status: | Confirmed → Triaged |
importance: | Wishlist → High |
Changed in juju-core: | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in juju: | |
importance: | High → Wishlist |
importance: | Wishlist → Low |
Changed in juju-core: | |
importance: | High → Medium |
To post a comment you must log in.
This is a good idea.
As a minor, it's not clear that the *new* version is necessary (the new version is always the one the script was bundled with).