-
Notifications
You must be signed in to change notification settings - Fork 16
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
PWX-36873: Add vault cooldowns #86
Conversation
* double "permission denied" REST error will put vault client into 5 minutes cooldown for all REST calls * can disable via `VAULT_COOLDOWN_PERIOD:disabled` Signed-off-by: Zoran Rajic <[email protected]>
Note, @adityadani , @CharudathGopal -- looks like the
|
Woops.. forgot to include UT with the original commit (fixed w/ follow-up f9fde71) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
This reverts commit 3aaff8a -- cause this breaks other integration tests.
Ok.. I can't failing I'll proceed w/ the squash-commit. |
* double "permission denied" REST error will put vault client into 5 minutes cooldown for all REST calls * can disable via `VAULT_COOLDOWN_PERIOD:0` Signed-off-by: Zoran Rajic <[email protected]>
VAULT_COOLDOWN_PERIOD:disabled
What this PR does / why we need it:
Turns out it is easy to overwhelm Hasicorp's Vault, and accidentally cause DDOS-attack
As a fix, we're adding
REST cooldown
for 5 minutes, to all Vault REST client callsPUT<key>
++RENEW<token>
both responded w/ "permission denied")Which issue(s) this PR fixes (optional)
Closes # PWX-36873
Special notes for your reviewer: