Comment 1 for bug 1949913

After hitting this bug again, and reading into the sources a bit, this seems like a critical bug. Apps relying on VaultAppKV (e.g. kubernetes-master, which I think is now kubernetes-control-plane) can end up clobbering each others' data.

Likely a similar issue occurs on VaultUnitKV, albeit mitigated somewhat if the unit IDs from the different apps don't collide. That doesn't matter in my current case re: Charmed Kubernetes, but it's worth calling out as well.

The core of the collision appears to be here: https://github.com/juju-solutions/layer-vault-kv/blob/39b0c7b38d59e0133d7fffe3849b4783c431e16d/lib/charms/layer/vault_kv.py#L246
(This is on the tip of the master branch at the time of writing.)

The only way I know of to avoid this issue at present is to avoid having multiple apps of the same name (via differnet models) using the same vault.