vault: install netbox and apptoken OpenBao plugin RPMs on bao nodes #519
Reference in New Issue
Block a user
Delete Branch "benvin/vault-plugin-netbox"
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
terraform-vault #115 registers
vault-plugin-secrets-netboxin the OpenBao plugin catalog pinned to the released v0.1.0 binary's sha256. OpenBao only registers/mounts a plugin whose binary is physically present in the plugin_directory (/opt/openbao-plugins); theopenbao-plugin-secrets-netboxRPM is published on rpm-internal but not yet installed on the bao nodes, so #115 fails to register until Puppet lays the binary down. Theopenbao-plugin-secrets-apptokenbinary is likewise published but missing from the bao package list, deferred from the apptoken engine's earlier deploy follow-up.Changes
openbao-plugin-secrets-netbox(pinned0.1.0) to the bao nodeprofiles::packages::includelistopenbao-plugin-secrets-apptoken(pinned0.1.0) to the same list, alongside the existing gpg/litellm/rancher/gitea plugin RPMs/opt/openbao-plugins, matching the plugin_directory OpenBao reads and the sha256 registered in terraform-vaultOrdering
This must apply (Puppet converge on the
roles::infra::storage::vaultnodes) BEFORE terraform-vault #115 is applied, otherwise #115's catalog registration fails on a missing binary.