vault-charm

  1. Bug #1883242
  2. Comment #13

Comment 13 for bug 1883242

Revision history for this message
Felipe Reyes (freyes) wrote : Re: [Bug 1883242] Re: consolidated etcd backend for Vault HA

On Sat, 2022-06-18 at 00:07 +0000, Nobuto Murata wrote:
> Having the new "initialize" action is cleaner but it requires yet
> another human intervention and also breaks the backward compatibility.
> i.e. existing bundles and process stop working.

For already deployed environments going through "juju upgrade-charm", on the
upgrade-charm hook we can mark go through the "initialize" logic (e.g.
set_flag() ) to stamp/lock what the storage backends will be from now on.

When it comes to bundles that "just work" today, you are right, they would need
to run a new action before running "vault operator init".

Maybe the vault charm could rely on "goal-state" to determine what will be its
storage configuration.