Title
m
mgagliardo
10/12/2022, 7:10 PMI'm working on setting up a repo that will handle the versioning/migrations of our schemas for SpiceDB - I saw there was a few github actions out there for testing, does anyone have a good example of a base template that handles schema migrations as well as testing via those/other actions?
Given that applied schemas are upserted - have others used a pattern similar to database migrations for handling schema changes?
j
Joey
10/12/2022, 7:42 PMwhat do you mean by a template that handles migrations?
m
mgagliardo
10/12/2022, 7:58 PMI was interested in any best practices around storing the schema file in a production setting - how to best handle migrations to avoid breaking changes (i.e. being able to test a schema change against the current state of the schema before it hits production)
It sort of feels like a problem similar to database migrations - they get applied on top of eachother and you can always ensure that they are compatible by re-running them against a clean instance
j
Joey
10/12/2022, 9:36 PMYeah, we have plans for formal tooling around migrations for that reason
But we are going to also write up a guide on best practices with existing tooling
m
mgagliardo
10/13/2022, 12:59 PMthanks @Joey !