What is the problem and why is it a problem
When a schema change is made it can create problems for downstream processes if it goes unnoticed.
A plan has been made to ensure that each facility is aware of any upcoming changes and can make any relevant updates before it is released.
-
A GitHub runner that check for changes to the schema, ideally any removals or changes to values, will put an alert on the PR that it includes breaking changes.
-
Any reviewers of the PR can check how these changes will effect downstream systems.
-
Facility specific: once a PR is merged to dev an alert can be sent out to the relevant people to make changes to/ double check downstream system/ processes.
What is the problem and why is it a problem
When a schema change is made it can create problems for downstream processes if it goes unnoticed.
A plan has been made to ensure that each facility is aware of any upcoming changes and can make any relevant updates before it is released.
A GitHub runner that check for changes to the schema, ideally any removals or changes to values, will put an alert on the PR that it includes breaking changes.
Any reviewers of the PR can check how these changes will effect downstream systems.
Facility specific: once a PR is merged to dev an alert can be sent out to the relevant people to make changes to/ double check downstream system/ processes.