Meltano

Hi,
I am bewildered: I spent way too long time debugging tap-jira (the singer-io variant), and long story short it seems although it did discovery apparently successfully, it didn’t produce a `tap.properties.json`  unless I specified the capabilities (state, discover, catalog) - and as a result it only outputted the schemas, no content. The hub page lists these three capabilities though, what difference could the capabilities key do?

It looks like <https://github.com/meltano/hub/blob/main/_data/meltano/extractors/tap-jira/singer-io.yml> has `properties` listed for `tap-jira` it sounds like you're saying it should be `catalog` instead of `properties` (Singer used to call them properties not catalog)

This tells meltano how to call the tap, if you run in debug mode you'll see the different ways the two call the tap (I think the difference is calling with `tap-jira --catalog catalog.json --config.json config.json` and `tap-jira --properties catalog.json --config.config.json`

If that's all it is then <https://github.com/meltano/hub/blob/main/_data/meltano/extractors/tap-jira/singer-io.yml#L3> has to change to `catalog` , normally someone puts properties on purpose though?

From the documentation here `<https://github.com/singer-io/tap-jira>`

```tap-jira -c config.json -p catalog-file.json```
is called with -p meaning properties seems right. Maybe the readme is wrong :shrug:

Thanks. Yeah that threw me too, I seem to remember running taps with —catalog, but here it was -p… but I just shrugged thinking I misremembered or something.