Thanks for joining us @oliver_laslett @ken_payne @julian_knight!

@aaronsteers it would be great to pick up the environment variables conversation again next week if possible. I don't think I 100% get it yet 😅 What you described tonight sounded a bit like namespaces rather than environments 🤔 i.e. scoped variables within a meltano deployment that apply to subsets of a project. When I think environments, I think of a complete copy of the entire meltano deployment with different configuration and versions (of meltano itself, of specific extractors/loaders, of airflow etc.) specifically to manage change (dev, test, ci-builds etc.). Does that make sense? I have included most of this in my comments in the issues too, so we don't have to pick it up here in slack 🙂

@ken_payne Yeah, makes sense. You're in good company with others giving similar feedback. Not sure if this is just a fault of not having a single "one-liner" to quickly describe the function, or else if the word "environment" is just too overloaded.