-
Notifications
You must be signed in to change notification settings - Fork 324
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
[WPB-8764] Backport changes from q1-2024
to develop
(Apr 23, 2024)
#4014
[WPB-8764] Backport changes from q1-2024
to develop
(Apr 23, 2024)
#4014
Conversation
… getting one2one conversations (#3918)
…sting and target user (#3923) Previous logic limited how many keys could be claimed for one user, but continued limiting claims on multiple users. This causes problems while creating conversations when a lot of key package claims are needed. This commit introduces a concept of specific_rate_limits which allow setting multiple rate limit zones in nginz. Here we use one for limiting how many key packages can be claimed by a user per target and another for limiting how many key packages claimed by a user for any target.
To ensure certificate revocations get active in a short time frame, disable caching of proxy results on client side by setting respective HTTP headers.
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.
The state of charts/smallstep-accomp
should match the one from the q1-2024
branch. But it doesn't. See
git diff origin/wpb-8764/port-missing-commits-from-q1-2024..origin/q1-2024 -- charts/smallstep-accomp
Thanks! I'll apply your observation. |
@smatting , now no more diff according to the command. Can you take another look? |
q1-2024
to develop (Apr 23, 2024)q1-2024
to develop
(Apr 23, 2024)
This includes:
Trackedy by https://wearezeta.atlassian.net/browse/WPB-8764.
Checklist
changelog.d