hey everyone. I'm currently building a custom tap for Bitbucket. I have reached the final stage and want to test it locally. However when I install it via

meltano add extractor tap-bitbucket --from-ref /absolute-path/tap-bitbucket/meltano.yml

Im getting the error

Plugin definition is invalid: missing properties (name, namespace).

My meltano plugin config looks like this

version: 1
default_environment: local
environments:
  - name: local
  - name: dev
  - name: prod
send_anonymous_usage_stats: false
plugins:
  extractors:
    - name: tap-bitbucket
      namespace: tap_bitbucket
      pip_url: -e .
      capabilities:
        - catalog
        - discover
        - state
        - about
      settings:
        - name: auth_username
          kind: string
          sensitive: true
        - name: auth_token
          kind: string
          sensitive: true
        - name: workspaces
          kind: string
        - name: repositories
          kind: string
        - name: start_date
          kind: string

Would appreciate some help, Im a bit lost here.

If your goal is to test it locally I wouldn't worry about adding the extractor with

--from-ref

I'd probably do this

cd /absolute-path/tap-bitbucket
meltano install
meltano invoke tap-bitbucket

by testing locally, i mean installing it in another repo/project and testing flow e2e. invoking the plugin from the plugin dir works fine, tests are green as well

https://docs.meltano.com/reference/command-line-interface/#:~:text=Using%20%2D%2Dfrom%2Dref%20allows,or%20testing%20of%20a%20plugin. I'd start with a draft PR to the meltano hub and follow those steps and the do the install from ref there as it looks like you're trying to use your meltano.yml file when the hub definition is slightly different I think specefically you'd need to drop the

plugins

, and

extracts

parent objects in your yaml file

I think I got it now. whenever you call

meltano add

it calls the hub first and gets specifications from it, including settings and other info. then maps it to the actual repo/location of the plugin. it works after flattening the schema and keeping only data from plugins.extractors

Yeah, the structure expected in

--from-ref

differs slightly from

meltano.yml

. What I've done in some of my taps, is add a plugin.yaml that I can pull even remotely as

meltano add extractor tap-clinicaltrials --from-ref=<https://raw.githubusercontent.com/edgarrmondragon/tap-clinicaltrials/main/plugin.yaml>

thank you @visch and @Edgar Ramírez (Arch.dev) its more clearer now