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

Adapt to Vault 0.8 lease endpoints #11

Closed
stklcode opened this Issue Jul 31, 2017 · 1 comment

Comments

Projects
None yet
1 participant
@stklcode
Owner

stklcode commented Jul 31, 2017

As of Vault 0.8.0 the current lease endpoints have been relocated and the current ones deprecated.

  • Lease Endpoints: The endpoints sys/renew, sys/revoke, sys/revoke-prefix, sys/revoke-force have been deprecated and relocated under sys/leases. Additionally, the deprecated path sys/revoke-force now requires the sudo capability.

To keep up with Vault, the connector should use the new endpoints. Have to decide whether to break compatibility with 0.7 or not...

@stklcode stklcode added this to the 0.7 milestone Jul 31, 2017

@stklcode stklcode self-assigned this Jul 31, 2017

@stklcode stklcode added test only and removed test only labels Aug 1, 2017

stklcode added a commit that referenced this issue Sep 24, 2017

Adaptation to Vault 0.8 endpoints for renew and revoke leases (#11)
Breaking backwards compatibility with Vault 0.7 and below.
@stklcode

This comment has been minimized.

Owner

stklcode commented Sep 25, 2017

Done.

Decided on breaking compatibility with Vault before 0.8, so Connector 0.7.0 will only be compatible with Vault 0.8 and above.

@stklcode stklcode closed this Sep 25, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment