@timvansteenburgh: I think you're tracking the wrong bug. Your issue looks to do with deploying a local charm from the filesystem. This bug is to deploy pre-deployed local charms from the controller, e.g.: `juju deploy local:xenial/foo-0 bar`
To everyone else:
I have this working, but it looks like there are some oddities both with placement and removing applications. E.g.
1. If I `juju deploy local:xenial/foo-0 bar`, the application is added, but no machine/container is provisioned
2. If I `juju remove-application bar`, I get an error "ERROR charm "local:xenial/bar" not found (not found)", but the application is removed successfully.
3. If I remove all the applications referencing this charm, I can still redeploy the charm from the controller (i.e. it's not being cleaned up). This is likely being addressed by another round of bug fixes, but is worth noting.
I need to investigate these to determine whether it's worth landing this with outstanding bugs. Because of that, this may not make b16. I'll post the decision in ~3h.
@timvansteenburgh: I think you're tracking the wrong bug. Your issue looks to do with deploying a local charm from the filesystem. This bug is to deploy pre-deployed local charms from the controller, e.g.: `juju deploy local:xenial/foo-0 bar`
To everyone else:
I have this working, but it looks like there are some oddities both with placement and removing applications. E.g.
1. If I `juju deploy local:xenial/foo-0 bar`, the application is added, but no machine/container is provisioned
2. If I `juju remove-application bar`, I get an error "ERROR charm "local:xenial/bar" not found (not found)", but the application is removed successfully.
3. If I remove all the applications referencing this charm, I can still redeploy the charm from the controller (i.e. it's not being cleaned up). This is likely being addressed by another round of bug fixes, but is worth noting.
I need to investigate these to determine whether it's worth landing this with outstanding bugs. Because of that, this may not make b16. I'll post the decision in ~3h.