Cerbos is the open core, language-agnostic, scalable authorization solution that makes user permissions and authorization simple to implement and manage.

Cerbos Community

I’m wondering about using yaml to define policies (production setting) - what are the reasons not to do this?

That is the primary way of defining policies so a good choice!

Is there a way to generate DB migrations from the YAML policies and store them in a database?

i.e. write YAML, but DB storage backend for policies? :smile:

You can post the policies to the Admin API which will manage writing them to the DB. 


That said, if you can define the policies in YAML do you need the database for your use case?

<https://docs.cerbos.dev/cerbos/latest/api/admin_api.html|https://docs.cerbos.dev/cerbos/latest/api/admin_api.html>

Makes sense, thx. Not a use case, was just exploring!