VAULT-37696: vault_plugin support for enterprise plugins #2707
+95
−3
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* modified: vault/resource_plugin.go modified: vault/resource_plugin_test.go * modified: vault/resource_plugin_test.go
chpag
changed the title
chpag
changed the title
siyer-corp
reviewed
Jan 8, 2026
siyer-corp
reviewed
Jan 8, 2026
fairclothjm
reviewed
Feb 2, 2026
Collaborator
fairclothjm
left a comment
fairclothjm
left a comment
There was a problem hiding this comment.
Thanks! Can we also update the docs page since sha is not required except for CE plugins? https://registry.terraform.io/providers/hashicorp/vault/latest/docs/resources/plugin#sha256-1
Contributor
Author
|
@fairclothjm : Doc has been updated to mark sha256 field as Optional, but still required for non-enteprise plugin |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR allow to use vault_plugin ressource for Vault Enteprise Plugin
As the sha should not be defined for enterprise plugin, it has been changed from mandatory to Optionnal
An additionnal check has been added in CustomzeDiff to add sha has mandatory if plugin version not ending with "+ent"
pluginIDRegex Regular Expression has been updated to allow "+" character in the version to allow "+ent"
when plugin is Enterprise, exclude sha from the attrbute retrievec by pluginRead(), so there is no mismatch between what is defined in the hcl code and what is put on the state file
Closes #2518
Checklist
Output from acceptance testing:
Community Note
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.