Comment 1 for bug 1826892

I've had a look at the charms' code to see what this might entail and one potential way to implement a second binding could be to add a new publish_url method [1] which would provide the url for a second space/binding should it be configured. That way the vault charm can optionally be configured on more than one space such that other charms can consume it without needing to be configured on its primary network.

[1] https://github.com/openstack-charmers/charm-interface-vault-kv/blob/master/provides.py#L45