Hello everybody. I'm new to meltano and I'm trying...
# announcements
j
Hello everybody. I'm new to meltano and I'm trying to configure pipelines to extract data from tap-outbrain to postgres. Currently we have a couple of accounts on outbrain so I would need to setup multiple pipelines for each account.
d
@jean_rumeau That's correct! If you add
tap-outbrains
as a custom plugin multiple times with different
name
s (which you can do by copy-pasting the
meltano.yml
definition), you can configure each of them differently. Or you can add the plugin once and configure it differently in each scheduled pipeline using env vars: https://meltano.com/docs/integration.html#pipeline-specific-configuration I'm also currently working on https://gitlab.com/meltano/meltano/-/issues/2390 (https://gitlab.com/meltano/meltano/-/merge_requests/1957), which will let you define
name: tap-outbrain
once, after which you can add new plugins with
name: tap-outbrain-some-account, inherit_from: tap-outbrain
that will inherit all configuration that you haven't explicitly overridden (like the account ID/creds).
j
Ok. Thanks. My problem Is that env configuration of pipeline is not being parsed
Is it possible to override tap and target configuratioin under schedule env property?
d
Ah OK, how are you testing that?
Is it possible to override tap and target configuratioin under schedule env property?
Yep, it should work as long as you use the correct
TAP_FOO_*
and
TARGET_FOO_*
env vars
Note that the "Run" button in the UI doesn't currently respect these env vars: https://gitlab.com/meltano/meltano/-/issues/2379
(Let me fix that right away so it can go into this afternoon's release)
j
Shouldn't be a problem if I run ELT from CLI using job_id?
Or there is a probe there too??, because I've try running ELT on CLI and got the same result.
`target-postgres | INFO PostgresTarget created with established connection:
user=taboola password=xxx dbname=taboola ....
d
Setting the
job_id
on
meltano elt
does not make it pick up the env for the schedule with the same name, because the schedule determines the
meltano elt
invocation arguments, including
job_id
, but not in the other direction
j
Oh, i see
d
If you're running
meltano elt
, you should provide the env vars explicitly
meltano schedule run <name>
would actually run a specific schedule with its env: https://gitlab.com/meltano/meltano/-/issues/2227
I agree this can be a little confusing
j
Ok. I've try both suggestions
meltano schedule run <name>
Will be available on the release also?
d
With a little bit of luck, yes 🙂
j
Thanks a lot!.
d
j
Worked perfect.
Thanks a lot
d
@jean_rumeau https://gitlab.com/meltano/meltano/-/issues/2390 took me a little longer to get over the finish line than expected, but I promise it was worth the wait: https://meltano.slack.com/archives/CP8K1MXAN/p1608746095055200