Implement Configuration in the Enviroment

[janhalen]

To ensure a proper cloud native foundation for deploying and scaling, all configuration should be stored outside the application and outside the source code itself. This way configs for multiple scenarios can be version controlled, collaborated upon and applied deploy-time instead of being part of a "static distribution" version.

This adheres to the 12 factor app design pattern: https://12factor.net/config

[janhalen]

This seems to be supported via Authentik blueprints: https://goauthentik.io/developer-docs/blueprints/

[janhalen]

Lets discuss how an Authentik container can be deployed up as stateless application with all the configs, flows etc. as external configration files...