Comment 0 for bug 1895185

Since commit db22a4652c6ec4bfbaf1b7cbd529f38a60a138df [0] for LP Bug#1826892 [1] if the bindings do not match on both ends of the secrets storage (vault-kv) relation the vault_url is not published even though role ids and tokens are. This leads to the relation being incomplete and is very difficult to diagnose.

We need a more robust solution that either errors out or very clearly communicates to the end user what needs fixing. The solution needs to resolve this bug and LP Bug#1826892.

I recall discussing the commit above at a sprint. I question the requirement to have matching bindings and it seems to me even if the bindings match but it is a routed environment (same space but different IP subnets) the current code would not work.

[0] https://github.com/openstack-charmers/charm-interface-vault-kv/commit/db22a4652c6ec4bfbaf1b7cbd529f38a60a138df
[1] https://bugs.launchpad.net/vault-charm/+bug/1826892