Add configurable rate limiting for dev/stage environments
- Add ORCHARD_LOGIN_RATE_LIMIT env var to Helm deployment template - Set relaxed rate limit (1000/minute) for dev/stage deployments - Production keeps strict default (5/minute) for security - Re-enable auth tests in CI (no longer excluded by marker) - Update test docstrings to reflect rate limit configuration
This commit is contained in:
@@ -81,7 +81,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
|
||||
- Improved pod naming: Orchard pods now named `orchard-{env}-server-*` for clarity (#51)
|
||||
|
||||
### Fixed
|
||||
- Fixed CI integration test rate limiting: added `auth_intensive` marker and excluded auth-heavy tests from deployed environments
|
||||
- Fixed CI integration test rate limiting: added configurable `ORCHARD_LOGIN_RATE_LIMIT` env var, relaxed to 1000/minute for dev/stage
|
||||
- Fixed duplicate `TestSecurityEdgeCases` class definition in test_auth_api.py
|
||||
- Fixed integration tests auth: session-scoped client, configurable credentials via env vars, fail-fast on auth errors
|
||||
- Fixed Content-Disposition header encoding for non-ASCII filenames using RFC 5987 (#38)
|
||||
|
||||
Reference in New Issue
Block a user