Ory is the largest open source community in the world for cloud software application security. We maintain advanced open source security software solving authentication, authorization, access control, application network security, and delegation. Ory implements a variety of industry and best-practice standards including OAuth 2.0 / OAuth 2.1, OpenID Connect, Zero Trust Networking, Google Zanzibar Policy Framework, FIDO2 U2F, WebAuthn, TOTP, and more.

Ory Community

well that's an embuggerance. It seems that env vars are not expanded inside an access-rules.yml file

I worked out a way with <https://github.com/a8m/envsubst>

and using  `inotifyd`  to watch for changes in the template folder, then run envsubst to populate the actual config files from the templates

works a treat. So when using as a docker volume, map the `templates` folder to the container so when you make any change to a template, `inotifyd` kicks in and regenerates the config files. Oathkeeper is watching for changes in the config yml and therefore reloads

I get bonus points for automating all of this in a docker container, and for also mapping the .env files, so I can experiment with all configs and envs without having to restart or rebuild  the  container :slightly_smiling_face:

Great solution, thanks for sharing! :raised_hands:
If you feel this could be useful to others and you ever want to contribute a minimal example for this in <https://github.com/ory/examples|github.com/ory/examples>, let me know (or just start a PR).
I will also try it out when I get around to it.