Comment 9 for bug 1287658

I can see supporting a flag to "juju expose <APP>:<ENDPOINT> <TO>" rather
than a generic "expose exposes to all". But I don't think the *charm*
should need to be aware of what CIDR it is being exposed to.

We would need changes to the hook tool "open-port" to be able to declare
"open this port for this endpoint", but in lieu of that, we could add
support for "juju expose APP SPACE" without charm changes.

But really it is the Operator that would be supplying CIDR/SPACE not the
*charm*.

On Fri, Oct 12, 2018 at 2:50 PM Junien Fridrick <email address hidden>
wrote:

> Yes, it does fall under the open/close port functionality of a charm -
> open-port accepting CIDRs would very likely cover our needs.
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1287658
>
> Title:
> Fine grain secgroup rules
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1287658/+subscriptions
>