Going from a remote charm to a local fork of it...
kapil.thangavelu at canonical.com
Wed Dec 7 02:48:40 UTC 2011
Excerpts from Clint Byrum's message of Wed Nov 30 17:40:29 -0500 2011:
> Kapil, I know your reply was a long time ago, so I've left the whole
> thing quoted.
> The sentence above is a problem, we need a 'switch-charm' command.
> The reason being, as a user of juju in production, I can't wait for
> *charmers* to fix the charm. If I were using Ubuntu and I had an *urgent*
> patch to mysql, I would follow this workflow:
> apt-get source mysql
> <fix the bug>
> debuild binary
> <push debs to my servers>
> After that, if the fix worked, and I feel its useful for other users,
> I *MIGHT* have time to send the fix back to Ubuntu.
> With juju, we need something similar, if I have done:
> juju deploy cs:mysql mydb
> And then the mysql charm is *breaking* my environment, or doesn't have
> some config option I need, I need to be able to do
> juju download-charm --repository=localcharms mydb
> <fix the bug in localcharms/mysql>
> juju switch-charm --repository=localcharms mydb local:mydb
> juju upgrade-charm --repository=localcharms mydb
> Yes, we want that fix to be contributed back, but that is completely
> secondary to juju being useful for lifecycle management of services.
I've filed a bug to track this functionality.
More information about the Juju