Just to provide a little context here, the client in my case is 'openstack-install' which pulls down the latest landscape-dense-maas bundle from the charmstore. Currently the versioned api url is hardcoded in the client and just like juju quickstart we'd have to update the client if/when the versioned url changed.
I do like the idea of having a `juju bundle get` or `juju charm get` in the interim while Juju gets a more official support for bundles. This keeps me from having to update the installer everytime a new Landscape is released or if the versioned api url changes.
Like David said this isn't high priority but would like to keep this on the radar moving forward.
Just to provide a little context here, the client in my case is 'openstack-install' which pulls down the latest landscape- dense-maas bundle from the charmstore. Currently the versioned api url is hardcoded in the client and just like juju quickstart we'd have to update the client if/when the versioned url changed.
I do like the idea of having a `juju bundle get` or `juju charm get` in the interim while Juju gets a more official support for bundles. This keeps me from having to update the installer everytime a new Landscape is released or if the versioned api url changes.
Like David said this isn't high priority but would like to keep this on the radar moving forward.
Thanks!