Add support for managing multiple databases with a --database flag and geni.toml configuration

slavakurilyak commented 2 months ago

Problem

Geni currently lacks a way to specify which database to target when running commands, making it challenging to manage multiple libSQL databases in a single project. Additionally, the tool relies solely on environment variables for configuration, which can be cumbersome for projects with multiple databases.

Proposed Solution

Introduce a new --database or -d flag for Geni commands to allow specifying the target database.
Implement support for a geni.toml configuration file to define multiple database configurations.

Example usage:

geni up --database project
geni up --database project-schema

Implementation Details

Add support for a geni.toml file with the following structure:

[project]
database_url = "libsql://project"
database_token = "your_database_token_here"

[project-schema]
database_url = "libsql://project-schema"
database_token = "your_database_token_here"

Modify the Geni CLI to:
- Accept and parse the new --database flag
- Read and parse the geni.toml file if present
- Fall back to environment variables if no geni.toml file is found or no --database flag is specified
Update the internal logic to use the specified database configuration when executing commands.
Update documentation to reflect the new functionality and geni.toml usage.

Benefits

Simplifies management of multiple databases within a single project
Improves workflow for multi-tenant database setups
Enhances CLI flexibility for database migrations and management
Provides a more convenient way to manage database configurations

Questions

Should we provide a way to set a default database in the geni.toml file?
How should we handle precedence between geni.toml, command-line flags, and environment variables?
Should we consider allowing environment variable overrides for database-specific configurations?

Acceptance Criteria

[ ] Geni CLI accepts a --database flag for all relevant commands
[ ] Geni supports reading and parsing a geni.toml configuration file
[ ] Commands correctly target the specified database using either the flag or geni.toml configuration
[ ] Documentation is updated to explain the new feature and geni.toml usage
[ ] Error handling is implemented for invalid database specifications and configuration issues

Your feedback and additional ideas for this feature are welcome!

emilpriver commented 2 months ago

Hey! Thank you for the contributing with this issue. I like the idea and I think I might tweak the database_token to allow to read ENV variable mainly as this is a secret. But I like the idea! :D

emilpriver commented 2 months ago

Btw, PRs are welcome :D

emilpriver / geni