FlexMeasures / flexmeasures / 39316551034

87%

push

github

Give the UI's API calls a rate-limit budget of their own, per user (#2700)

* Count the general API rate limit per account, rather than per user

All users and API clients of an account now share one budget for the default limit,
which is the budget the account's plan sets, so that the account page shows the only budget there is.
Unauthenticated requests are still counted per IP address, and the health endpoints stay exempt.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MSo5u94LjgXLeMJ51Pja39
Signed-off-by: F.N. Claessen <claessen@seita.nl>

* Changelog: the default rate limit counts per organisation

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MSo5u94LjgXLeMJ51Pja39
Signed-off-by: F.N. Claessen <claessen@seita.nl>

* Docs: reflow how the two limits count, leave the trigger limit's key to #2679, and say that the UI spends the default budget, too

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MSo5u94LjgXLeMJ51Pja39
Signed-off-by: F.N. Claessen <claessen@seita.nl>

* Shorten the docstring on what the default limit is counted against

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MSo5u94LjgXLeMJ51Pja39
Signed-off-by: F.N. Claessen <claessen@seita.nl>

* Give the UI's API calls a rate-limit budget of their own, per user

The UI's pages call the API with the user's session, while integrations send a token.
Counting both against the account's budget let a runaway integration lock the account's users out of the UI,
and let browsing spend the budget the integrations need.
The tests of the account's default limit now call the API with a token, like the integrations they stand for.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MSo5u94LjgXLeMJ51Pja39
Signed-off-by: F.N... (continued)

23 of 23 new or added lines in 2 files covered. (100.0%)

22142 of 25510 relevant lines covered (86.8%)

0.87 hits per line