<!channel> Happy Friday! A day later than usual, b...
# announcements
f
<!channel> Happy Friday! A day later than usual, but we’ve got a Meltano release for ya! meltano Meltano v1.87.0 ✨ New • #2456 - Let project plugin definitions and config be defined in multiple individual YAML files. Thanks, Matthew Thurman for the inspiration and first draft! ⚠️ Breaks • #2977 Disable the Explore and Dashboards tabs in the UI by default. See the Data Analysis docs for details on how to enable it. singer logo  SDK - no release required this week.
s
awesome! is there any migration steps required for the "multiple yml" files?
f
Nope - existing things still work as-is - totally optional (https://meltano.com/docs/project.html#multiple-yaml-files)
v
Got a demo of structured logs that didn't get released but no demo of yaml files that did get released? 😄 Just a little poke
I deserve all the poking as well so feel free 😛
a
Challenge accepted! 😄 https://meltano.slack.com/archives/C02HHKD73TL/p1636153829003100?thread_ts=1636152955.001500&amp;cid=C02HHKD73TL I've recorded a quick video demo if anyone is interested. (Friendly pokes always appreciated.)
s
Love love love this multiple yml feature. Makes it so much easier to navigate to tap config at a glance
m
As a thought for the “multiple yml” feature, do think eventually it will be possible to define the external dependencies (pip_url’s) in a separate
.yml
and have the rest of the configuration live in other files (like a Gemfile for Ruby / pyproject.toml for Python)? I’m asking because that would make building Meltano in a build system / docker faster as the dependencies would only need a reinstall when that particular file changes.