Meltano

I really like how meltano separates the extractor name from the underlying singer tap name. I have two separate postgres databases that I need to extract from, so I am able to cleanly have two separate names and configurations, even though the underlying singer tap is the same (tap-postgres)

Nice! At some point we may solve that natively with configuration profiles (<https://gitlab.com/groups/meltano/-/epics/51>), but for the moment that workaround should work perfectly :slightly_smiling_face:

Of course, you can also override config on a per-`meltano elt` basis using env vars, even if the same tap is used, but then you can't store the different config values in `meltano.yml` anymore

This doesn't even feel like a workaround. I like giving each extractor a different name

<@U06C8NEFG2Z> I'm glad :smile: There's just one downside: you'll have the exact same tap package installed inside `.meltano` multiple times, wasting disk space. With profiles, you'd be able to refer to them by name as well, but use the same underlying package: `meltano elt tap-postgres@profile-1 ...`

But either way, that doesn't actually work fully yet, and what you're currently doing does :slightly_smiling_face:

That would be a good optimization. But a nice to have. Right now I have no problem with the lost disk space