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

Jump to bottom

Adapt to Vault 0.8 lease endpoints #11

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

Adapt to Vault 0.8 lease endpoints #11

stklcode opened this issue Jul 31, 2017 · 1 comment
Assignees
@stklcode
Labels
compatibility
Milestone
0.7

Comments

@stklcode
Copy link
Owner

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 mentioned this issue Aug 4, 2017
Closed
@stklcode stklcode mentioned this issue Aug 28, 2017
Closed
stklcode added a commit that referenced this issue Sep 24, 2017
@stklcode
Adaptation to Vault 0.8 endpoints for renew and revoke leases (#11)
e002fc7 
Breaking backwards compatibility with Vault 0.7 and below.
@stklcode
Copy link
Owner Author

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.

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

@stklcode stklcode

Labels
compatibility
Projects
None yet
Milestone
0.7
Development

No branches or pull requests
1 participant
@stklcode