Okay - so I’m very new to Meltano (and singer.io). I’m just getting things setup and tested and I wanted to make sure I understand something about the selection process. I’m using tap-salesforce. I did a discovery and noted that in

.meltano/run/tap-salesforce/tap.properies.json

there were a bunch of objects and fields already selected. I wanted to add the task object so I ran

meltano select tap-salesforce Task "*"

. After running this, it seems like everything in the json file got set back to not selected and now the

meltano.yml

file is being used to track my selection. Am I understanding what happened correctly. I’m guessing that as long as a tap supports the meltano select wrapper, that is the easier way to maintain what is selected.

@bryan_wise Yep, you've got it. If you run

meltano config tap-salesforce list --extras

, you'll see that the default value for the

_select

(https://meltano.com/docs/plugins.html#select-extra) is the list defined here: https://gitlab.com/meltano/meltano/blob/master/src/meltano/core/bundle/discovery.yml#L854-860

Very cool. Thanks for explaining the default selection during discovery process. That helps a lot!

And it is indeed recommended that you let Meltano handle the generation of the catalog: https://meltano.com/docs/integration.html#extractor-catalog-generation