VAULT-34830 actions(plugin-update): update plugins from enterprise

[ryancragun]

Description

Support updating both CE and Enterprise plugins when the plugin update workflow targets vault-enterprise instead of CE.

This needs to be merged in conjunction with https://github.com/hashicorp/vault-plugin-release/pull/62 right before we do the merge workflow cutover.

TODO only if you're a HashiCorp employee

• Backport Labels: If this fix needs to be backported, use the appropriate backport/ label that matches the desired release branch. Note that in the CE repo, the latest release branch will look like backport/x.x.x, but older release branches will be backport/ent/x.x.x+ent.
  • LTS: If this fixes a critical security vulnerability or severity 1 bug, it will also need to be backported to the current LTS versions of Vault. To ensure this, use all available enterprise labels.
• ENT Breakage: If this PR either 1) removes a public function OR 2) changes the signature
  of a public function, even if that change is in a CE file, double check that
  applying the patch for this PR to the ENT repo and running tests doesn't
  break any tests. Sometimes ENT only tests rely on public functions in CE
  files.
• Jira: If this change has an associated Jira, it's referenced either
  in the PR description, commit message, or branch name.
• RFC: If this change has an associated RFC, please link it in the description.
• ENT PR: If this change has an associated ENT PR, please link it in the
  description. Also, make sure the changelog is in this PR, not in your ENT PR.

PCI review checklist

• I have documented a clear reason for, and description of, the change I am making.
• If applicable, I've documented a plan to revert these changes if they require more than reverting the pull request.
• If applicable, I've documented the impact of any changes to security controls.

Examples of changes to security controls include using new access control methods, adding or removing logging pipelines, etc.

[github-actions]

CI Results:
All Go tests succeeded! ✅

[github-actions]

Build Results:
All builds succeeded! ✅

[fairclothjm]

If I am understanding correctly, this will only work if we always include the +ent version metadata in the plugin version. We don't currently do that for plugins that have always been Enterpise-only. For example https://github.com/hashicorp/vault-plugin-secrets-kmip/tags. However, if this is the approach you would recommend, then we can probably start doing that?

[ryancragun]

No worries. I think I'll just pass in whether or not it's an enterprise plugin from the caller which can be derived from the plugins.yaml?

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Project	Deployment	Preview	Comments	Updated (UTC)
vault-ui	✅ Ready	Preview	Comment	Aug 12, 2025 5:15pm

[fairclothjm]

LGTM!