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

[Storage-backend][vault pki] Add storage backend vault pki to template certs from vault #774

Open
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

tw3rp
Copy link

@tw3rp tw3rp commented Feb 18, 2019

This PR includes changes to add a new storage backend vault pki to template certs from vault

  1. "Inherits" all the methods from the vault backend so authentication and all the flags remain the same
  2. Certs are issues by listing keys as /mountpath/rolename/commonname eg. /pki/issue/my-role/www.example.com and the keys returned are /pki/issue/my-role/www.example.com/certificate and /pki/issue/my-role/www.example.com/private_key. This is so because it goes against confd design principles to pass in multiple arguments to a key
  3. The cert and the key must be templated to the same file because it is an open issue to template to multiple files (Create multiple config files from templates #256)
  4. An example script is put in so we can split them into individual files once templated.

This is for issue #731 to template certs as a new backend

@tw3rp tw3rp mentioned this pull request Feb 18, 2019
* add file backend to quick start guide

* add formatting to file backend debug call

* fix my poorly exec'ed fork update

[storage-backend][vault PKI] Add storage backend - vaultpki
initial commit

initial commit
removed unused files

[vaultpki] Fix test

[vaultpki] add other key values

test removing the test file

test removing the test files

try zookeeper

fix tests
fix tests so it returns zero
@tw3rp
Copy link
Author

tw3rp commented Apr 7, 2019

small write up on how it works https://rprabhu.dev/2019/vault-confd-automation/

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

Successfully merging this pull request may close these issues.

None yet

1 participant