| 2015-04-04 03:13:01 |
David Britton |
description |
It would be nice to have a "get this bundle" url so that we could use it with juju deployer locally, or modify it and use it with quickstart. Unfortunately, bundles are still not always fire-and-forget as some require configuration before deploying.
Right now, you can grab from
https://api.jujucharms.com/charmstore/v4/~landscape/bundle/landscape-dense-maas/archive/bundle.yaml
And you will get the latest, however, if /v4/ changes in a year, your links are broken. Is there a better way?
Not a huge deal of course, just one that might be good for long term health of links to the store. |
Update:
Sorry, I think the original description was too much about links and apis which confused the issue. We are just requesting a stable way to retrieve a charm bundle. Not a web page about a bundle, but the bundle text (or the whole directory most likely) itself.
Something similar to the idea of `charm get` would be just fine. [*]
The analogy raised by Richard of how juju quickstart currently works is spot on, I just want to type something like:
juju get-bundle u/landscape/landscape-dense-maas
... and the bundle shows up.
[*] - I say "the idea of" since last time I used it it retrieved a bzr branch, and not necessarily what was in the store. :)
-------------------------------
Original description:
It would be nice to have a "get this bundle" url so that we could use it with juju deployer locally, or modify it and use it with quickstart. Unfortunately, bundles are still not always fire-and-forget as some require configuration before deploying.
Right now, you can grab from
https://api.jujucharms.com/charmstore/v4/~landscape/bundle/landscape-dense-maas/archive/bundle.yaml
And you will get the latest, however, if /v4/ changes in a year, your links are broken. Is there a better way?
Not a huge deal of course, just one that might be good for long term health of links to the store. |
|
