Details
-
Type:
New Feature
-
Status: Open (View Workflow)
-
Priority:
Major
-
Resolution: Unresolved
-
Component/s: hashicorp-vault-pipeline-plugin
-
Similar Issues:
Description
The present Hashicorp Vault Pipeline Plugin depend on Hashicorp Vault Plugin. The Hashicorp Vault Plugin was modified to support KV2 secrets from vault but don't have a release that include the feature. And we also need the support for this feature in the Hashicorp Vault Pipeline plugin to be able to use the feature in a Jenkinsfile.
Attachments
Activity
| Field | Original Value | New Value |
|---|---|---|
| Rank | Ranked higher |
| Description | The present Hashicorp Vault Pipeline Plugin depend on Hashicorp Vault Plugin. The Hashicorp Vault Plugin was modified to support KV2 secrets from vault but don't have a release that include the feature. And we also need the support for this feature in the Hashicorp Vault Pipeline plugin as well to be able to use the feature in a Jenkinsfile. | The present Hashicorp Vault Pipeline Plugin depend on Hashicorp Vault Plugin. The Hashicorp Vault Plugin was modified to support KV2 secrets from vault but don't have a release that include the feature. And we also need the support for this feature in the Hashicorp Vault Pipeline plugin to be able to use the feature in a Jenkinsfile. |
yeah that would be most desirable thing to do to solve such issues with dependency between two plugins.
Is there a ticket for merging the two plugins? I mistakenly thought that this functionality was already part of the main plugin, which honestly would make a lot more sense.
Erik Blomqvist
added a comment - Is there a ticket for merging the two plugins? I mistakenly thought that this functionality was already part of the main plugin, which honestly would make a lot more sense.
I suggest we deprecate hashicorp-vault-pipeline-plugin and move the logic into hashicorp-vault-plugin