Tim Möhlmann 4eaa3163b6 feat(storage): generic cache interface (#8628) ... # Which Problems Are Solved We identified the need of caching. Currently we have a number of places where we use different ways of caching, like go maps or LRU. We might also want shared chaches in the future, like Redis-based or in special SQL tables. # How the Problems Are Solved Define a generic Cache interface which allows different implementations. - A noop implementation is provided and enabled as. - An implementation using go maps is provided - disabled in defaults.yaml - enabled in integration tests - Authz middleware instance objects are cached using the interface. # Additional Changes - Enabled integration test command raceflag - Fix a race condition in the limits integration test client - Fix a number of flaky integration tests. (Because zitadel is super fast now!) 🎸 🚀 # Additional Context Related to https://github.com/zitadel/zitadel/issues/8648		2024-09-25 21:40:21 +02:00
..
auth_request_test.go	chore(tests): use a coverage server binary (#8407)	2024-09-06 14:47:57 +02:00
client_test.go	fix: correctly check app state on authentication (#8630)	2024-09-17 11:34:14 +00:00
keys_test.go	chore(tests): use a coverage server binary (#8407)	2024-09-06 14:47:57 +02:00
oidc_test.go	chore(tests): use a coverage server binary (#8407)	2024-09-06 14:47:57 +02:00
server_test.go	chore(tests): use a coverage server binary (#8407)	2024-09-06 14:47:57 +02:00
token_client_credentials_test.go	fix: correctly check user state (#8631)	2024-09-17 13:21:49 +00:00
token_exchange_test.go	chore(tests): use a coverage server binary (#8407)	2024-09-06 14:47:57 +02:00
token_jwt_profile_test.go	feat(storage): generic cache interface (#8628)	2024-09-25 21:40:21 +02:00
userinfo_test.go	chore(tests): use a coverage server binary (#8407)	2024-09-06 14:47:57 +02:00