-
Notifications
You must be signed in to change notification settings - Fork 156
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
Broken Compatibility for write for pki #6
Comments
I could use a pip list, environment you are working in, what command you are running and the output |
We have used this construct :
and inside in data is |
And the message is? |
I also need the version of ansible-module-hashivault you are running |
it may be that leading '/' on your secret name. Is that secret on the mount point /secret or /{{vault_pki_path}}? |
What gets returned is
|
Tried with latest version from this repo also using hvac 0.2.16 |
btw we actually have forked your repo and made improvements to previous version. So it looks like this functionality was never in your version https://github.com/generiklimited/ansible-modules-hashivault , sorry! |
I'm not following on what the problem is with There was a change around 2.9 where if the secret name starts with / it is assumed absolute path meaning you are specifying the mount point. It doesn't assume that the mount point ins /secret anymore. I assume this is what you are seeing. |
If you have any more PRs, that'd probably make life easier for both of us. |
Mount point is correct, however, client.write returns data from vault response, and it is required for use with PKI. ( as when you write to pki/issue/role it returns the certificate and key ) I will write the patch it requires for your latest version when I get a spare time. |
https://pypi.python.org/pypi/ansible-modules-hashivault/2.10.0 new release should have what you want |
I'm going to close this out, if you have something else, reopen or make a new issue, thanks for the PR! |
We were using your module to issue pki certs from vault, now we do not get the data back sent by vault only a message written by your module... it would be useful to actually have it working again
The text was updated successfully, but these errors were encountered: