From b534b8528d8c27577c5cbfdf5f649401fe4dfa03 Mon Sep 17 00:00:00 2001 From: Ben Vincent Date: Sat, 18 Jul 2026 16:35:17 +1000 Subject: [PATCH] Bump rancher plugin catalog to v0.1.1 (bearerToken fix) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit v0.1.0 minted non-functional tokens (returned status.value instead of status.bearerToken; every cred/rotation 401'd). v0.1.1 fixes it. Re-register the catalog entry with the v0.1.1 binary sha256 so OpenBao launches the fixed plugin. - config/plugins/vault-plugin-secrets-rancher.yaml sha256 -> v0.1.1 (9e597cd9…d5955, verified against both v0.1.1 RPMs). Requires the v0.1.1 RPM installed on the vault nodes (puppet) and a 'vault plugin reload -plugin=vault-plugin-secrets-rancher' after apply. --- config/plugins/vault-plugin-secrets-rancher.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/config/plugins/vault-plugin-secrets-rancher.yaml b/config/plugins/vault-plugin-secrets-rancher.yaml index 5fc2d1d..64bac42 100644 --- a/config/plugins/vault-plugin-secrets-rancher.yaml +++ b/config/plugins/vault-plugin-secrets-rancher.yaml @@ -4,8 +4,8 @@ # Puppet (openbao-plugin-secrets-rancher RPM -> # /opt/openbao-plugins/vault-plugin-secrets-rancher). # -# sha256 pins the released v0.1.0 binary; bump it in lockstep with any RPM +# sha256 pins the released v0.1.1 binary; bump it in lockstep with any RPM # upgrade or OpenBao will refuse to launch the plugin. type: secret command: vault-plugin-secrets-rancher -sha256: "d2b17f45b5fa9e6549443fec3ba22f17ef575d2d811c14324187dc9904ec574a" +sha256: "9e597cd9512a0629f940141dc6611bf95eaf165abcb52470eee027bf467d5955" -- 2.47.3