Organising apiserver facades

[roger peppe]

Getting all of that facade-specific logic out of the apiserver package
seems like a great idea to me. I don't think it would take *too* much work
to factor the helper logic into its own package entirely, with no
dependencies on the facades. The client is actually almost there already
with its APICaller interface as common currency - we should really follow
the intent of this old comment of William's
<https://github.com/juju/juju/blob/develop/api/interface.go#L285-L289>.The
manifold issue is the interesting one - work out a good solution to that
and the rest'll come quite quickly, I feel.

It would be marvellous to get parts moving more freely in Juju again -
losing big fan-out dependency graphs is a good way to move in that
direction, I'm pretty sure.

  rog.


On 6 July 2017 at 10:55, Andrew Wilkins <andrew.wilkins at canonical.com>
wrote:

> The juju/apiserver package currently has a whole lot of facade packages
> within it, as well as some other packages related to authentication,
> logging, and other bits and bobs. I find it difficult to navigate and tell
> what's what a lot of the time.
>
> I'd like to move the apiserver facade packages into a common "facades"
> sub-directory:
>   apiserver/facades/application
>   apiserver/facades/client
>   apiserver/facades/controller
>   etc.
>
> Any objections? Or alternative suggestions?
>
> Cheers,
> Andrew
>
> --
> Juju-dev mailing list
> Juju-dev at lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/
> mailman/listinfo/juju-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20170709/37872648/attachment.html>