Just a little something I discovered the hard way: the merits of specifying a very simple meltano job rather than just a bare

meltano run

command. Say you're running meltano in docker, but want to use a different target plugin (maybe you're gradually migrating your tap-target combos over to meltanolabs variant of

target-postgres

). If you have your command specified as a job, then you only need to alter

meltano.yml

and redeploy your meltano image to switch target. If you've specified a

meltano run

command elsewhere in your infra, you need to make changes there too, perhaps your IaC code, which can be much more involved to approve & deploy.