Today, we are excited to release Meltano version 1.35.0, which (among other things) makes it easier to manage and version control a Meltano project’s configuration by having meltano config
store values in meltano.yml
by default, instead of the system database.
Sensitive and environment-specific values can still be stored in the system database via the UI or meltano config <plugin> set --store=db <key> <value>
.
Learn more about managing the configuration of your plugins
Excited to try it out?
To upgrade your local installation of Meltano, activate the appropriate Python virtual environment and run meltano upgrade
from inside a Meltano project, or pip3 install --upgrade meltano
from anywhere else. If you’re running Meltano inside Docker, run docker pull meltano/meltano
.
What else is new?
The list below (copied from the changelog) covers all of the changes made to Meltano since the release of v1.34.2 on May 29:
New
- #2013 Add
--store
option tomeltano config
with possible valuesdb
andmeltano_yml
- #2087 Add
--plugin-type
option tomeltano config
andmeltano invoke
- #2088 Add
meltano upgrade
subcommandspackage
,files
,database
, andmodels
Changes
- #2064 Print environment-specific instructions when
meltano upgrade
is run from inside Docker - #2013 Have
meltano config
store in meltano.yml instead of system database by default - #2087 Skip plugins that are not configurable or invokable when finding plugin by name in
meltano config
andmeltano invoke
Fixes
- #2080 Don’t try to overwrite .gitignore when upgrading Meltano and project
- #2065 Don’t have
meltano upgrade
complain whenmeltano ui
‘sgunicorn
isn’t running - #2085 Don’t change order of object and set values when meltano.yml is updated programatically
- #2086 Ensure “meltano config –format=json” prints actual JSON instead of Python object