You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copied from https://bugs.launchpad.net/juju/+bug/1820080, as it seems like having charm-tools wrap juju deploy is the better path forward. Basically, it would be nice if there were a single command for deploying a bundle that would build any local charms as necessary and grab the rest from the charm store. It's unlikely to be able to happen in juju itself, since we don't want to add charm-tools as a dependency to juju deploy, but it might make sense to have e.g. charm deploy-bundle that would take care of this.
The text was updated successfully, but these errors were encountered:
We also discussed the possibility of adding a --deploy option to charm build and adding support to charm build to detect if it's called against a bundle, specifically if the bundle contains references to local charms, and to perform a build on those local charms before doing the deploy.
It works great for deploying, though I think I'm going to add another command or so, and have something like juju bundle deploy and juju bundle destroy, as right now I don't think there's a handy way to remove everything in a bundle.
Copied from https://bugs.launchpad.net/juju/+bug/1820080, as it seems like having
charm-tools
wrapjuju deploy
is the better path forward. Basically, it would be nice if there were a single command for deploying a bundle that would build any local charms as necessary and grab the rest from the charm store. It's unlikely to be able to happen in juju itself, since we don't want to addcharm-tools
as a dependency tojuju deploy
, but it might make sense to have e.g.charm deploy-bundle
that would take care of this.The text was updated successfully, but these errors were encountered: