Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Test: revisit kamu-cli-e2e-inmem #1125

Open
s373r opened this issue Mar 5, 2025 · 0 comments
Open

Test: revisit kamu-cli-e2e-inmem #1125

s373r opened this issue Mar 5, 2025 · 0 comments
Assignees
@s373r
Labels
rust Pull requests that update Rust code

Comments

@s373r
Copy link
Member

s373r commented Mar 5, 2025

Context

We currently use the default SQLite base for both modes of operation (single-tenant, multi-tenant). Thus, there is no longer any room for inmem repositories in the production code path.

Expectations

  • Remove the ability to run kamu-cli with "in memory" configuration (DatabaseConfig::InMemory)
  • Review the kamu-cli-e2e-inmem and kamu-cli-e2e-sqlite tests for differences and keep only one group, since in general, these tests have become duplicative of each other
@s373r s373r added the rust Pull requests that update Rust code label Mar 5, 2025
@s373r s373r self-assigned this Mar 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@s373r s373r

Labels
rust Pull requests that update Rust code
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@s373r