hashicorp-vault-plugin icon indicating copy to clipboard operation
hashicorp-vault-plugin copied to clipboard

Jenkins plugin to populate environment variables from secrets stored in HashiCorp's Vault.

Results 122 hashicorp-vault-plugin issues
Sort by recently updated
recently updated
newest added

the variable names for the `vaultSSHUserPrivateKeyBinding` jobdsl credentials binding are not reflected in the job after it is created, instead just the defaults are displayed. the job does run correctly...

Hello please tell me how I can save all variables to a file without declaring all variables in "def secrets"

Hi, I have 2 namespaces in Vault, create 2 approle credentials in each namespace. So I have 2 credentials in Jenkins, I want to use both of them, but now...

Hi, in our project setting we are using a single Jenkins instance to run tasks (e.g. deploy, test, etc.) against several different systems. Due to our infrastructure constraints and guidelines...

We had introduced additional abstract class to add token expiry awareness in last release. This made it 3 levels of abstract classes. After looking into it closely, I think probably...

When using dynamic credentials is there any house cleaning required (eg should it be deleted)? ` import hudson.util.Secret import com.cloudbees.plugins.credentials.CredentialsScope import com.datapipe.jenkins.vault.credentials.VaultTokenCredential import org.apache.commons.lang.RandomStringUtils def vaultToken="myfancytoken" def randomString = org.apache.commons.lang.RandomStringUtils.random(8,...

How about adding 1 more environment variable to enable bypass SSL verification step during initial secret fetch for JCasC in Hashicorp vault plugin at: https://plugins.jenkins.io/hashicorp-vault-plugin/

Hi - when running the following pipeline on a worker node, the following exception occurs: ``` `node { def secrets = [ [path: 'my-path/dev/searches/users/admin', engineVersion: 1, secretValues: [ [envVar: 'PASSWORD',...

Add ability to generate dynamic credentials to use in build step ``` node { def secrets = [ [path: 'azure/creds/myazurerole', engineVersion: azure, secretValues: [ [client_id: 'myID', client_secret: 'mySecret'], ]], ]...

I've noticed that secrets provisioned on the dynamic engine (eg. GCP) no longer get revoked when a pipeline is finished with them (exits the withVault block), and instead the generated...