LCORE-1249: config for SQLite should be separated

[tisnik]

Description

LCORE-1249: config for SQLite should be separated

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
• Benchmarks improvement

Tools used to create PR

• Assisted-by: N/A
• Generated by: N/A

Related Tickets & Documents

• Related Issue #LCORE-1249

Summary by CodeRabbit

• Tests
  • Updated benchmark test configuration to use an alternative database setup.

---

Note: This release contains only internal testing modifications with no user-facing changes.

[coderabbitai]

Walkthrough

The benchmark test configuration has been updated to use a SQLite configuration file instead of a lightspeed-stack configuration file. The configuration_filename fixture now references benchmarks-sqlite.yaml, while all benchmark logic and database setup remain unchanged.

Changes

Cohort / File(s)	Summary
Benchmark Configuration tests/benchmarks/test_app_database.py	Updated fixture to return SQLite benchmark configuration file instead of lightspeed-stack configuration.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• LCORE-1249: stub for benchmarks #1084: Introduced the test_app_database.py benchmark test and the original benchmarks-lightspeed-stack.yaml configuration that this PR replaces.

🚥 Pre-merge checks | ✅ 3

✅ 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 accurately describes the main change: switching the benchmark configuration from lightspeed-stack to SQLite-specific configuration, which aligns with the PR objective of separating SQLite configuration.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

No actionable comments were generated in the recent review. 🎉

---

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.}