GitHub
08/04/2026, 12:55 PMmeltano compile).
Future iterations beyond initial MVP could:
1. Run test on all plugins (inline `meltano test --all`)
2. Warn on plugin config issues:
1. Non-existent lock files.
2. Missing capabilities declarations.
3. Unpinned pip URLs.
3. Warn on instances of deprecated or soon-to-be-deprecated features.
4. Warn if any required plugin config has been declared.
5. Warn if any provided config values do not match their setting's type, or their setting does not have a declared type, or their setting is not declared.
6. Warn if any settings defined as secrets are declared in yaml in clear text.
7. Run automatically after failure.
Future iterations could also consider a --fix to resolve the subset of things that are auto-resolvable, such as:
1. Running lock on plugins that don't have lock files.
2. Applying simple yaml refactoring, as needed if future meltano.yml versions expect a different layout. Such as migrating from maps to lists.
Depends on:
• #6876, #7148
Cc @WillDaSilva, @tayloramurphy
meltano/meltanoGitHub
08/04/2026, 12:55 PM