One of my favorite features that we released this year in atmos are “profiles”. It comes with the sober realization that there is never just one context for configuration. It changes whether you are running in CI, if you are a developer working in a few environments, or a power user leveraging all that atmos has to offer. Traditionally, this would be solved by environment variables. But then how do you consistently mange those variables in each context? When new variables are introduced how are those communicated? By taking the approach of using atmos profiles you can skip convoluted work arounds. Set one environment variable and manage everything else as pure configuration. See https://atmos.tools/changelog/atmos-profiles/

with this you could implement stack level vendor.yaml files 🐕

Wow, 🤯 didn't think about that

Stack level profiles, stack level atmos configs

Profiles are really powerful. I think it's a great first-class way of solving many challenges in a config-native way.

yeah without any weird bash wrappers or a workflow that runs atmos workflows