FlexMeasures / flexmeasures / 39134190831

88%

push

github

Admin command to reset an account's rate limits (#2680)

* Count triggers per account only, and deprecate FLEXMEASURES_API_RATE_LIMIT_KEY

Counting triggers per account and asset, or per user, made plans harder to show and to support.
The setting is still accepted, but ignored, with a warning at startup if it asks for anything other than "account".

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>

* Drop plan.rate_limit_key, now that triggers are always counted per account

Removes the column and its enum type in a migration, the --rate-limit-key option from add plan and edit plan, the column from show plans, and the trigger scope from the account page.

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: triggers are counted per organisation only

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>

* Add flexmeasures edit reset-rate-limit, to reset an account's rate limits

Context:
- #2676: an account whose integration was fixed after it ran into a rate limit had to wait out the window

Change:
- reset_rate_limits() clears the counters of the limits in effect for the account (its plan's or the server-wide ones), as the limit's amount is part of the counter's key
- The trigger counter is the account's; the default limit is still counted per user, so each of the account's users' counters is cleared
- --limit trigger|default resets only one of them, and a limit the account is exempt from is skipped with a warning

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

59 of 60 new or added lines in 4 files covered. (98.33%)

21851 of 25194 relevant lines covered (86.73%)

0.87 hits per line