pyjuju

The revision number in formula metadata is not very useful to users

Bug #810648 reported by Clint Byrum
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
pyjuju
Fix Released
Undecided
William Reade
pyjuju eureka

Bug Description

The revision number in metadata.yaml is easy to forget to change. Silently, one will be deploying the same formula over and over while wondering why their changes haven't been recognized. Ensemble should warn users when the hash of the formula they're asking to deploy or upgrade is different from an existing formula with the same revision number.

Revision history for this message
Kapil Thangavelu (hazmat) wrote :

this has been addressed as part of the auto-increment revision on upgrade, revision is also separate from the metadat file now.

Changed in juju:
assignee: nobody → William Reade (fwereade)
milestone: none → eureka
status: New → Fix Released
Revision history for this message
Kapil Thangavelu (hazmat) wrote :

for the deploy case the problem remains

Revision history for this message
Kapil Thangavelu (hazmat) wrote :

the underlying issue is that our charm hashes aren't consistent, since their zip file based, and zip will keep file metadata (timestamp) that make the overall archive content change. ideally we could do some consistent hashing here and do a warning about this problem on deploy.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.