Feature proposal: meltano config validate
#9057
Replies: 3 comments
-
|
My thoughts on this are also related to meltano/sdk#1519, an issue about being able to know if an SDK plugin has valid settings based on user defined groups of settings. If these groups of settings are in the SDK, and present in an SDK plugin when a user runs If the plugin doesn't have these groups, the behaviour stay the same where |
Beta Was this translation helpful? Give feedback.
-
|
@aaronsteers I think is a duplicate of a duplicate:
I like either validate / lint - though lint to me implies it's going to take action potentially on your file. |
Beta Was this translation helpful? Give feedback.
-
|
This would be a duplicated of
But not a dupe of: Since #7285 needs to do much more than validating, its scope will necessarily be a superset of many component commands. We need to first write the component tests and actions before we can pair them into a wholistic 'lint' operation. For example, #7285 mentions calling |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
This could also be invoked inline as part of
meltano test ....We can also print inline as warnings:
meltano config set --interactive.meltano lint#7285)Ideally these would also print requirements or explain requirements to users:
meltano config list, andmeltano config set --interactiveprior to asking for input.Beta Was this translation helpful? Give feedback.
All reactions