Meltano 2.0 - including deprecations and "Hub-first" approach to plugins
IMPORTANT:
- Please use the v2.0 label for anything that should be "in scope" for the release!
- For a full v2.0 burndown list, please use this link.
- The timeline of when each v2.0 issue is expected to be picked up is here.
- The list of issues with the v2.0 label but no Iteration are here.
- The 2.0 Launch Spreadsheet is here
In an effort to move more quickly towards our goal of being the end-to-end DataOps platform, we want to remove some legacy BI features (dashboards, models, and transforms) which are being replaced by open source BI tools such as Lightdash, Superset, and mProve. We also want to make sure the Hub is the primary source of truth, and introduce a hard requirements that all plugin definitions are locked within projects going forward (#3031 (closed)).
If we bump to a new major version we could trim out these parts of the product which are no longer part of our long-term vision, and at the same time introduce breaking changes around Add lock artifacts during `meltano add` for sta... (#3031 - closed) and Support `meltano add` directly from Hub (#3283 - closed) so that we can cleanly migrate to the Hub as source of truth.
Roundup of items which might be good to bucket into a 2.0
release:
- Add lock artifacts during `meltano add` for sta... (#3031 - closed)
- Support `meltano add` directly from Hub (#3283 - closed)
- Remove support for
dashboards
plugins (#3293 (closed)) - Remove support for
models
plugins (#3293 (closed)) - Move to a revised yaml plugin spec, per Translate all tap and target yaml files on the ... (hub#203 - closed)
Maybe: Remove support fortransforms
plugins (no issue open yet) and/or migrate to hub.dbt.com packages (#2794 (closed)).- Disable the auto-add feature which automatically installs
transform
andmodel
plugins when they match the tap name or namespace. - Maybe: Remove support for
env_aliases
and replace with settings aliases, per Use "setting.aliases" as alternative to "env_al... (#3209 - closed) - Make each of these plugin-level settings a one-... (#3431 - closed)
- Maybe: ADR - Require environment for any invocation (#3275 - closed)
- Consider how to migrate from generic utilites t... (#3218 - closed)
Cc @tayloramurphy, @afolson, @edgarrmondragon, @pandemicsyn, @kgpayne