I'm a very strong -1 on this idea. Providers are Juju specific, and the other libraries should focus on exposing a useful Go API.
Tim On 25/03/16 10:12, Eric Snow wrote: > Perhaps we should move the implementation of some providers over to > the repos for the projects with which the providers interact (and then > just import them in providers/all). Then those providers would be > more likely to stay up-to-date in the face of changes in the project, > particularly backward-incompatible ones. For example: > > * provider/maas -> github.com/juju/gomaasapi/maasprovider > * provider/lxd -> github.com/lxc/lxd/lxdprovider > * ... > > or something like that. It's not a perfect solution nor a complete > one, but it should help. > > -eric > -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
