There's times where I have a harder time getting access to my tap data (for various reasons this one is because I'm trying to dev on a linux machine and the tap I'm running requires a Windows box). To work around this I do something like hop on the machine I want data from, run

meltano invoke tap-name > tap-name.singer

then I take that file and I can develop locally with my other taps/targets locally without needing to have the special access for that one tap. Now comes the annoying part.

cat tap-name.singer | meltano invoke target-postgres

works, but I need to provide a target_schema for

target-postgres

So I use this bash script

#/bin/bash
export TARGET_POSTGRES_DEFAULT_TARGET_SCHEMA="TAP_ACTIVEDIRECTORY"
cat tap-ad.singer | meltano invoke target-postgres

But I don't love it. It's almost like I want something like

meltano run (cat tap-ad.singer as tap-ad) target-postgres

meltano invoke --static-stdin=tap-name.singer target-postgres ? (where static-stdin is smart enough to detect target schema from filename or something) 😁 and while im spit balling. Could be nice if meltano supported saving data AND context so that you can "replay" a session later.

meltano invoke --save-replay=mysave.singer tap-name
meltano invoke --replay=mysave.singer target-name

😄 Replay is curious