This was an oversight. I will look into adding this shortly considering the whole reason I wrote the plugin was for use with the aws backend, but havent had the opportunity to test against it yet. Thanks for bringing it to my attention.

Sounds great. I appreciate your work on this.

kgatdula The latest release should fix this issue. It does however change the usage slightly. https://github.com/jenkinsci/hashicorp-vault-plugin

I just published via maven. It may take time until the plugin is updated in the update center. The new docs are available however in the github readme and the jenkins wiki page: https://wiki.jenkins-ci.org/display/JENKINS/HashiCorp+Vault+Plugin

I'm going to leave this ticket open until you have the opportunity to test. Take note of the caveats section in the readme/wiki.

ptierno I tried to install this via the update center today with no luck. I downloaded the plugin and installed it manually. it seems to work great. here's a snippet of configuration I ended up using.

def aws_secrets = [
    [$class: 'VaultSecret', path: 'aws/creds/deploy',
      secretValues: [
        [$class: 'VaultSecretValue', envVar: 'AWS_ACCESS_KEY_ID', vaultKey: 'access_key'],
        [$class: 'VaultSecretValue', envVar: 'AWS_SECRET_ACCESS_KEY', vaultKey: 'secret_key']]]
  ]

kgatdula Thanks for the feed back. Not sure what is taking so long for the 1.1 release to become available via update center. if its not there by the end of the weekend i'll inquire about it. Thanks for the feedback. marking this as resolved.