Just want to make it clear that I'm not saying that 12-factor as a whole is obsolete, I'm only talking about 3rd factor (Config). Yes, it's possible to impleme

Just want to make it clear that I'm not saying that 12-factor as a whole is obsolete, I'm only talking about 3rd factor (Config). Yes, it's possible to implement dynamic configuration on top of environment variables using templates and signals, but you'd have to implement a lot of non-trivial logic yourself (how to have different values based on the context, how to deliver new versions of templates, caching, thread safety, logging, etc). And you would have to use a wrapper to access it. At this point, you essentially building a custom configuration management system and environment variables become an implementation detail. And you are stepping away from using the benefits of environment variables: clear separation by deployments and language-agnostic nature. The main point of Lekko is not fancy UI and API (in fact Lekko doesn't really have an API, it just requires you to express your configs as pure functions). The main point of Lekko is that you should treat your configs as code (but with a different deployment pipeline) and Lekko helps you with it. > Having in-app service-API integration with language-specific SDKs for wiring up configuration is an recognized as an antipattern for reasons and a motivation behind 12-factor. Can you elaborate on this? 12 factor talks about changing configs independently from code on a per-deployment basis. Lekko supports that among other things. It feels like you are projecting an experience of using a specific solution (like Consul or something) to all configuration management tools.