When I do a `meltano install` it apparently is try...
# plugins-general
f
When I do a
meltano install
it apparently is trying to connect to the (system?) database. Why would it need to connect to a database to install plugins?
v
What's the error? Not sure on #2 for why it needs to connect to install plugins, I'm sure there's a reason
I've had it happen, and sometimes I Just need to plop another .db in there, I tend to just run
meltano init
then copy over the db created in
.meltano
into the
.meltano
directory that doesn't have one and move on
f
Hmm. I'm trying to adapt the Dockerfile that metlano creates with a add files docker to create a Lambda function image. It's a Lambda function, so it won't have a local DB, it will connect to an Aurora DB. But it shouldn't need one when installing plugins. I don't understand why install would need to connect to the system database to install plugins, but a --help shows a --database-uri as an option, so there must be some reason. All it should be doing is creating venvs and installing python modules for the plugins...
v
I didn't design meltano so I don't know off hand, but I'm sure there's a reason that's logical, otherwise an issue should go in
🤷
You have me curious
f
Yea, docs say nothing about creating or using the system database for init, install, or add CLI options. And the system DB that I have, in Aurora, has nothing saved I can see that has anything to do with plugins. There's a plugin_settings table, but nothing in it. The only thing that has anything non-default is jobs for the jobs that were run. So I don't know why it has to connect to the database just to prep and install plugins.
v
Yeah the source code is fairly straight forward I think I found where it happens at least https://gitlab.com/meltano/meltano/-/blob/master/src/meltano/cli/install.py#L31
@pass_project
decorator defined here
<https://gitlab.com/meltano/meltano/blob/master/src/meltano/cli/params.py#L28>
Using
install
does a check to be sure the DB is setup and any migrations are complete before running
project
is used a bunch by install I guess, still not clear to me why yet either
e
All commands run migrations (if any) but in the case of
meltano install
it's not important which database they run on https://meltano.slack.com/archives/CFG3C3C66/p1593183132343800?thread_ts=1593131174.342600&amp;cid=CFG3C3C66