adam_roderick
08/11/2021, 11:47 AMpoetry run tap-xyz --discover --config config.json
is giving different results than meltano invoke tap-xyz --discover --config config.json
. Any tips on how I can troubleshoot this?adam_roderick
08/11/2021, 12:11 PM.meltano
directory and running meltano install
again, I am able to see the updatesadam_roderick
08/11/2021, 12:11 PMdouwe_maan
08/11/2021, 2:44 PM.meltano/extractors/tap-xyz/venv
have been outdated?douwe_maan
08/11/2021, 2:44 PMmeltano invoke
is https://gitlab.com/meltano/meltano/-/issues/2627, which affects the discovered catalog when running the tap in sync mode, but shouldn’t make a difference when you explicitly run with --discover
adam_roderick
08/11/2021, 2:47 PM.meltano
directory. I'm trying to understand the development flow for tap development--should I delete the .meltano
directory and rerun .meltano install
anytime I want to test code changes through the meltano CLI?douwe_maan
08/11/2021, 3:13 PMpip_url
directly at the dir, yes, because pip install <pip_url>
will install the package inside .meltano
. If you’ve installed in editable/dev mode (pip_url: -e path/to/package
), it will be symlinked instead of copied over, so changes should be picked up automatically. That won’t work with Poetry-based projects though. When using the SDK to develop a new tap/target, we recommend omitting pip_url
and pointing executable
directly at the executable wherever you’re developing the tap, so that it will always use the latest version as welldouwe_maan
08/11/2021, 3:13 PMadam_roderick
08/11/2021, 3:22 PMaaronsteers
08/11/2021, 3:29 PMtap-mysource.sh
script created by the cookie cutter. The cookie cutter should also contain a sample meltano.yml file which demonstrates this.adam_roderick
08/11/2021, 3:30 PM