Thanks Aaron, can you add the information and arguments you'd like to make
to the doc. Perhaps add a Missing to the doc and provide the information
you'd like to see returned and such there. Does this need both charms and
bundles? As two calls, in one call, etc.
Rick
On Tue, 08 Jul 2014, Aaron
The idea is that the charm store is growing a lot since the original api
was done. It's gaining a first class entity in bundles, it'll be growing
identity support, search functionality, and other metadata. The api space
is growing and needs to be able to be consistent with other tools as they're
On 9 July 2014 15:20, Gustavo Niemeyer gust...@niemeyer.net wrote:
Is there a reason to reinvent the API from the ground up, instead of
extending what exists today?
We actually started out by thinking that we'd make something
backwardly compatible with the old charm store API, but
we're
We've done a lot of work recently improving the reliability of our
test suite. Unfortunately, feature work has been introducing new tests
that are intermittently failing.
http://juju-ci.vapour.ws:8080/job/github-merge-juju/1/console
FAIL: machine_test.go:1750: MachineSuite.TestWatchInterfaces
