LCORE-298: Conversation cache factory

[tisnik]

Description

Refactoring: ConversationCache -> ConversationCacheConfiguration

Type of change

• Refactor
• New feature
• Bug fix
• CVE fix
• Optimization
• Documentation Update
• Configuration Update
• Bump-up service version
• Bump-up dependent library
• Bump-up library or tool used for development (does not change the final image)
• CI configuration change
• Konflux configuration change
• Unit tests improvement
• Integration tests improvement
• End to end tests improvement

Related Tickets & Documents

• Related Issue #LCORE-298

Summary by CodeRabbit

• New Features

  • Expanded conversation cache configuration with selectable backends (in-memory, SQLite, Postgres).
  • Added centralized validation to prevent conflicting backend selections.

• Refactor

  • Renamed the conversation cache configuration to conversation_cache_configuration; update your config to use the new field name.

[coderabbitai]

Warning

Rate limit exceeded

@tisnik has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 20 minutes and 21 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 1f2311a and 8c6c62d.

⛔ Files ignored due to path filters (2)

• docs/config.png is excluded by !**/*.png
• docs/config.svg is excluded by !**/*.svg

📒 Files selected for processing (5)

• docs/config.puml (5 hunks)
• src/configuration.py (2 hunks)
• src/models/config.py (2 hunks)
• tests/unit/models/config/test_conversation_cache.py (15 hunks)
• tests/unit/test_configuration.py (2 hunks)

Walkthrough

Renames the conversation cache configuration type to ConversationCacheConfiguration, adds backend-specific options and centralized validation, updates AppConfig to expose conversation_cache_configuration and a private cache attribute, and aligns unit tests with the new names and accessors.

Changes

Cohort / File(s)	Summary of changes
Config model rename & expansion src/models/config.py	Renamed ConversationCache → ConversationCacheConfiguration; added backend-specific configs (memory/sqlite/postgres); introduced check_cache_configuration validator enforcing exclusive backend selection; updated global Configuration.conversation_cache type and default_factory.
AppConfig accessor updates src/configuration.py	Added private _conversation_cache: Optional[Cache]; renamed property conversation_cache → conversation_cache_configuration, returning ConversationCacheConfiguration while still reading from underlying _configuration.conversation_cache.
Unit tests: model config tests/unit/models/config/test_conversation_cache.py	Updated imports/references from ConversationCache to ConversationCacheConfiguration; adjusted instantiations and expectations accordingly.
Unit tests: AppConfig tests/unit/test_configuration.py	Updated attribute access from conversation_cache to conversation_cache_configuration; retained existing error-path assertions.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

Possibly related PRs

• LCORE-298: configuration for conversation cache #563 — Introduces the original ConversationCache and AppConfig accessor that this PR renames and expands; directly related to the same configuration surface.

Poem

I hop through fields of config bright,
Renaming burrows by moonlit night.
Caches choose one cozy den, not three—
Memory, sqlite, or postgres tree.
With whiskers twitch, I validate,
Then thump “all set!”—ship the state.
🐇✨

Pre-merge checks and finishing touches and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The title "LCORE-298: Conversation cache factory" is concise and directly related to the changeset because it references the conversation cache work and the associated ticket, giving quick context to reviewers. Although the changes primarily rename and expand the configuration type to ConversationCacheConfiguration (so "factory" emphasizes an implementation aspect rather than the exact API rename), the title still meaningfully describes a real part of the change.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}