zitadel/internal/integration/config
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
..
client.yaml chore(tests): use a coverage server binary (#8407) 2024-09-06 14:47:57 +02:00
cockroach.yaml add github action for integration tests 2023-04-25 18:11:04 +03:00
docker-compose.yaml chore(tests): use a coverage server binary (#8407) 2024-09-06 14:47:57 +02:00
postgres.yaml chore(test): set connection lifetimes for postgresql (#8586) 2024-09-11 07:45:02 +00:00
steps.yaml chore(tests): use a coverage server binary (#8407) 2024-09-06 14:47:57 +02:00
system-user-key.pem feat: push telemetry (#6027) 2023-07-06 08:38:13 +02:00
zitadel.yaml feat(storage): generic cache interface (#8628) 2024-09-25 21:40:21 +02:00