oncall-engine/engine/settings
Ildar Iskhakov 1b7ada4315
Add database migrations linter (#1020)
# What this PR does

This PR adds
[django-migration-linter](https://github.com/3YOURMIND/django-migration-linter)
to keep database migrations
 backwards compatible

- we can automatically run migrations and they are zero-downtime, e.g.
old code can work with the migrated database
 - we can run and rollback migrations without worrying about data safety
- OnCall is deployed to the multiple environments core team is not able
to control

See [django-migration-linter
checklist](https://github.com/3YOURMIND/django-migration-linter/blob/main/docs/incompatibilities.md)
for the common mistakes and best practices


## Which issue(s) this PR fixes

## Checklist

- [ ] Tests updated
- [ ] Documentation added
- [ ] `CHANGELOG.md` updated

---------

Co-authored-by: Joey Orlando <joey.orlando@grafana.com>
2023-02-06 16:01:37 +08:00
..
__init__.py World, meet OnCall! 2022-06-03 08:09:47 -06:00
base.py Add database migrations linter (#1020) 2023-02-06 16:01:37 +08:00
ci-test.py Restore email notifications (#621) 2022-10-19 12:32:56 +01:00
dev.py Fix local dev setup slowness (#1270) 2023-02-02 09:08:48 +00:00
helm.py Allow multiple database and celery broker types (#582) 2022-10-04 09:25:53 +01:00
hobby.py Allow multiple database and celery broker types (#582) 2022-10-04 09:25:53 +01:00
prod_without_db.py Move FCM relay logic into a celery task (#1137) 2023-01-13 19:28:34 +00:00