[FEATURE] multiple "configuration" support

[julien]

Is your feature request related to a problem? Please describe.
No, not at all.

Describe the solution you'd like
I really like the --config flag and I was wondering if it could be possible to add support for multiple configurations. I think that most developers using this tool have a local database, maybe another local database only used for testing purposes, and then a database for each environment in which the deploy their code.

Describe alternatives you've considered
The alternative is to add all your configurations in the $HOME/.dblab.yaml file and comment them, except the one you're going to use.

Additional context
dblab is a nice tool so thanks a lot for making it.

[danvergara]

Hi @julien. Thanks for the suggestion and the kind words.

First of all, I need more details to get this done as quickly as possible. I'm thinking of adding multiple connection sections to the config file and adding a new flag that tells the cli which config is to be used. The default value is the first one (if there's more than one). Is this aligned with the expected behavior you're thinking of?

[julien]

Hey @danvergara,

You can take your time do implement this, there are probably multiple ways to do it, I just thought I'd propose it.
Your suggestion seems OK to me. You could also let the --config accept a value, for example:

dblab --config dev
# or dblab --config [configuration_name]

To make that happen you probably need to add a name property to each configuration too.

If the configuration exists, that's what you use, if it doesn't you can show an error and exit.
If the --config flag is passed without a value, then you just choose the first one defined in the configuration file (or alternatively, add a default (boolean) to each configuration so you know which one the user wants to use a the default).

Let me know what you think when you can.

[danvergara]

Hey @julien. Sorry for the delayed response. You were right, I was into multiple things. But I could come up with something to address your feature request. It's still a work in progress so far, but you can check it out in #138.

[julien]

Hi @danvergara no worries and thanks a lot for implementing this.