write-charm doesn't mention the need to bump version numbers when iterating charms
Bug #1015657 reported by
Jonathan Lange
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| pyjuju |
Triaged
|
Low
|
Unassigned | ||
Bug Description
write-charm describes the process of writing a charm, and even talks a little about making a change to a charm that you're working on and have just deployed.
However, it doesn't mention the need to bump the version number when re-deploying in order to get juju to pay attention to the new changes.
This leads to confusion and wasted effort when charm developers puzzle over why their latest change didn't work.
Revision history for this message
| William Reade (fwereade) wrote | #1 |
| Changed in juju: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| Changed in juju: | |
| importance: | Medium → Low |
To post a comment you must log in.
FWIW, deploy -u will do this for you automatically. We should definitely mention this prominently in the docs, though.