Hi Everyone, in the section about adding a plugin to your Meltano project under the executable key it references a local test script in the comment with the example being a .sh script. I've just used the cookiecutter template for the Meltnao tap-sdk and there's no .sh script in there. I feel like there is a step I am missing. I've created a Meltano environment using meltano init and then have another folder where the cookiecutter code for the tap is.

You can create one. If you want it to run in a separate python env, you can use poetry to install, activate shell and then just call the tap's entry point

Thanks @kk I'm still a little unclear from the docs how to reference the custom tap from the meltano repository that I have set up

Think the docs are a little out-of-date here from when poetry didn't yet properly support an editable local install (see here). You should just be able to use

pip_url: -e .

in your

meltano.yml

. After running

meltano install

, you should be able to run

meltano invoke <your-custom-tap>

.

Thanks @Reuben (Matatika) that's what the default Meltano.yml looks like from the cookiecutter. I've run that in the custom tap directory and it's installed. From the docs I was a little confused as it reads like a user is meant to set up a separate Meltano repository and load the custom tap into there.

Yep, think you have everything set up correctly then. 🙂

I also found this which is more up to date than the docs and explains it all step by step https://meltano.com/blog/how-to-build-a-custom-extractor-with-meltano/

I love seeing community folks helping each other out 😄. I popped a PR to fix the outdated usage of a shell script: https://github.com/meltano/meltano/pull/6650

The

-e /path/to/tap-my-custom-source

is under

pip_url

with the

executable

set to the name of the tap. Happy to open a PR for this?

please do @jazzy! (Personal note not to make updates in the browser 🤦‍♂️ )