Bump rancher plugin catalog to v0.1.1 (bearerToken fix) #96
Reference in New Issue
Block a user
Delete Branch "benvin/rancher-plugin-v0.1.1"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Why
v0.1.0 of the rancher plugin minted non-functional tokens — it returned
status.value(the secret fragment) instead ofstatus.bearerToken(ext/<name>:<secret>), so every cred and every root rotation 401'd against Rancher. Fixed in plugin v0.1.1 (PR #2, released).Changes
config/plugins/vault-plugin-secrets-rancher.yamlsha256 → v0.1.1 binary9e597cd9…d5955(verified against both v0.1.1 RPMs). Re-registers the catalog entry so OpenBao launches the fixed binary.Deploy coordination
vault plugin reload -plugin=vault-plugin-secrets-rancherso the running plugin swaps to v0.1.1 (its sha must match this catalog entry).