Code-first configuration of schema, roles and permissions

It would be great if schemas, roles and permissions could be managed via code. Often custom permissions contain logic that is of a fairly technical nature and should ideally be _versioned_ and _repeatable_ between dev/staging/prod environments. By supporting code-first configuration, a team of developers could collaborate on things like permission logic and easily keep their local development environments in sync via source control. Ideally permissions logic could then also be unit tested. Currently schemas, roles and permissions are configured in the UI and stored in the database. It is of course possible to create schema snapshots and export permissions and roles via the API, however this approach does not fit naturally into a DevOps flow with multiple developers and multiple environments. The general idea is that schemas, roles and permissions could be developed in code (e.g. yaml) and applied to the database the next time directus is started. An extension of this would be…