GitHub
02/24/2026, 7:44 PM*) next to required fields in the UI, based on the plugin's settings_group_validation property, like `tap-gitlab`'s:
settings_group_validation:
- ['api_url', 'groups', 'start_date']
- ['api_url', 'projects', 'start_date']
The array can contain one or more lists of setting names, each of which is a combination of settings that constitute a valid/complete configuration. In the case of tap-gitlab, this means that api_url and start_date are always required, and that groups, or projects, or both, but not neither, should also be set.
In the UI, we only show an asterisk next to settings that are always required (so not groups or projects), but don't enable the "Save" button until at least one group matches completely. This means that it's not clear to the user what's wrong when all of the apparently required fields are filled in, while the "Save" button is still disabled, but this hasn't caused an issue yet because it's usually clear to users that they have to pick a specific group or project.
In the output of meltano config <plugin> list, we can easily display asterisks where appropriate when there's only a single group of valid setting names, but I'm not sure yet what to do about groups and projects in the example above.
meltano/meltanoGitHub
02/24/2026, 7:44 PM