[Bug 1797148] Re: vault: support operator configuration of kv mountpoint

[James Page]

Test packages with patches in:

  https://launchpad.net/~james-page/+archive/ubuntu/vault-production

I've verified these within a Rocky deployment; secrets where stored
correctly in the configured backend (charm-barbican) rather than the
default 'secret' backend.

** Changed in: barbican (Ubuntu)
       Status: Triaged => In Progress

** Changed in: python-castellan (Ubuntu)
       Status: Triaged => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to barbican in Ubuntu.
https://bugs.launchpad.net/bugs/1797148

Title:
  vault: support operator configuration of kv mountpoint

Status in castellan:
  In Progress
Status in barbican package in Ubuntu:
  In Progress
Status in python-castellan package in Ubuntu:
  In Progress

Bug description:
  The vault integration currently hard-codes the KV mountpoint on
  'secrets' - this is the name of the enabled by default KV store in
  vault, but is probably not typical in a hardened deployment where
  multiple KV mountpoints may be used for different purposes.

  Defaulting to 'secrets' is fine, but having a config option to allow
  end user configuration would be beneficial.

To manage notifications about this bug go to:
https://bugs.launchpad.net/castellan/+bug/1797148/+subscriptions