Oathkeeper Access Rules as Yaml

[designermonkey]

Preflight checklist

• [x] I could not find a solution in the existing issues, docs, nor discussions.
• [x] I agree to follow this project's Code of Conduct.
• [x] I have read and am following this repository's Contribution Guidelines.
• [ ] I have joined the Ory Community Slack.
• [ ] I am signed up to the Ory Security Patch Newsletter.

Ory Network Project

No response

Describe your problem

I want to be able to provide my oathkeeper.accessRules in yaml like is accepted for oathkeeper.config. The current setup is hardcoded to expect rules as a string, which it dumps into a json file in a config map.

Describe your ideal solution

Everything we do is in yaml as we use helm and kustomize to configure our deployments, so having the ability to provide yaml rules instead of json (as a string) would be good.

Idea: change accesRules from a string to:

oathkeeper:
  accessRules:
    format: "json|yaml"
    content: (yaml or json)

Workarounds or alternatives

Other than not use the helm chart beyond dumping it from helm template, I am unsure anad I am trying to figure that out right now.

Version

0.58.0

Additional Context

No response