mojo should be able to publish charm & asset revisions from one environment and consume them in another

[Tom Haddon]

Mojo should have a mechanism for publishing the state of all charm & assets deployed in an environment (branch and revision).

It should also have a mechanism for consuming that in another environment.

Essentially what this means is a phase/helper script that publishes in some format what's been defined in a collect file, but including the specific revision numbers for items that don't define a revision number. And then another helper script that can assemble those charms and assets (essentially an "on-the-fly" collect phase).

So we have a collect file like this, for example:

apache2 lp:charms/trusty/apache2
haproxy lp:charms/trusty/haproxy

Mojo would then generate something like this:

apache2 lp:charms/trusty/apache2;revno=200
haproxy lp:charms/trusty/haproxy;revno=150

Another environment can then use this as a collect file to replicate the charms from the other environment. Mojo should have a way of doing this easily.

[Tim Kuhlman (timkuhlman)]

The first step is getting codetree to report what revisions it collected. The first change for that is at https://code.launchpad.net/~timkuhlman/codetree/results-objects/+merge/312311

[Tim Kuhlman (timkuhlman)]

The codetree portion has now merged in Mojo this change takes the revisions from codetree and makes a collect file out of them https://code.launchpad.net/~timkuhlman/mojo/collection-results/+merge/312313

After this change that collect file can be copied in place manually but another change will be needed to allow another run of mojo to automatically consume the new collect file.