I have been working on a few reimplementation of taps on the hub but now using the SDK. When I install using custom

pip_url

I can see this message in the logs:

2023-04-17T12:19:56.055035Z [debug    ] Found plugin parent            parent=tap-freshdesk plugin=tap-freshdesk source=hub

Will the presence of a plugin on the hub already affect the operation of my new plugin variant? I found that some capabilities like

catalog

wasn't working correctly for my new version even though it should. The existing version on the hub only had

state

as a capability. Would what's on the hub affect my new ground-up implementation? Do I need to explicitly define my tap's

capabilities

in meltano.yml?

Its possible that there are some artifacts from the hub version in your project like a lock file so I'd recommend running

meltano remove tap-freshdesk

then re-add it as a custom plugin https://docs.meltano.com/concepts/plugins#custom-plugins with a custom definition

Got it, so the hub contains info like capabilities for known taps, so it doesn't appear in meltano.yml, but if you build you own taps then capabilities needed to be explicitly stated in meltano.yml?

Yep - when you install from the hub you get a json lock file that includes all of the extra metadata about the plugin so it doesnt clutter your meltano.yml since its not something you'd edit, although you could override it if needed. When you use a custom plugin you need to define that metadata manually.

...sound of a penny dropping... thankyou 🙂