Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configure consul backend in hashicorp-vault > 1.5.x #48

Closed
ghost opened this issue Mar 21, 2016 · 1 comment
Closed

Configure consul backend in hashicorp-vault > 1.5.x #48

ghost opened this issue Mar 21, 2016 · 1 comment

Comments

@ghost
Copy link

ghost commented Mar 21, 2016

Greetings,

I'm currently working on upgrading our internal vault wrapper cookbook to use hashicorp-vault 2.1.1 from 1.5.x and I'm running into some issues with configuring consul as the secret backend.

With 1.5.x we'd use:

node.override['vault']['config']['backend_type'] = 'consul'
node.override['vault']['config']['backend_options']['address'] = '127.0.0.1:8500'
node.override['vault']['config']['backend_options']['path'] = 'vault'

to generate a configuration file with the following:

"backend": {
    "consul": {
      "address": "127.0.0.1:8500",
      "path": "vault"
    }
},

However, this no longer appears to work with 2.x and instead yields:

"backend": {
    "inmem": {
    }
}

I can't see anything significantly in the diffs between 1.5.0 and 2.1.1 that would stop this from working. Please advise!

Many thanks!

@ghost
Copy link
Author

ghost commented Mar 21, 2016

Oh, I see! The node attribute name has changed from node[vault] to node[hashicorp_vault] in https://github.com/johnbellone/vault-cookbook/blob/v2.1.1/recipes/default.rb.

@ghost ghost closed this as completed Mar 21, 2016
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

0 participants