I’m trying to write a nice meltano.yml file for my tap, is there a way to mark a setting as optional? I’m looking at the UI, and it seems anything declared in the meltano file pops up as required in the dialog box.

I’m looking at the UI, and it seems anything declared in the meltano file pops up as required in the dialog box.

You’d use

settings_group_validation

for that:

settings_group_validation:
- ['filepath','default_target_schema']

is the meltano.yml file primarily used when taps are on the meltano hub? When it’s just on github somewhere, I guess it doesn’t make as much of a difference because it needs to be manually added anyways?

@Henning Holgersen can you expand a bit on your question here?

meltano.yml

is used both for plugins in meltano Hub and custom ones. For example. even for Hub plugins, you can override settings, capabilities, etc.; and configure the plugin. Custom plugins do need to declare capabilities, settings, etc. in

meltano.yml

.

Thank you as always, I got it working now. My second question is somewhat moot, but to expand; If I install a plugin from meltano hub, I can run

meltano add <…>

, followed by

meltano ui

. And then I can fill it all out in a nice browser. If I install manually, I have to fill out the

meltano.yml

first, and then run

meltano install

. I suppose I could still start the UI and configure the extractor, but I imagined it is very uncommon for people who install manually to use the UI. But again, this is moot.

settings_group_validation

was the key I was looking for and now my tap is really starting to shape up.