Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Auto data health checks #149

Open
northdpole opened this issue Feb 3, 2022 · 1 comment · May be fixed by #195
Open

Auto data health checks #149

northdpole opened this issue Feb 3, 2022 · 1 comment · May be fixed by #195
Assignees
@northdpole
Labels
P1 High Priority
Milestone
Data health checks

Comments

@northdpole
Copy link
Collaborator

once the auto-backups are in place
create an action that downloads the latest database from heroku and compares it to the latest known good state.
If the known good state data isn't equivalent to the heroku ones, fail.

This might be possible by just dumping dbs, filtering out heroku custom things and checking for string equivalence
@northdpole northdpole added this to the Data health checks milestone Feb 3, 2022
@northdpole
Copy link
Collaborator Author

problem: known good state needs to be a heroku backup, it cannot be a local sqlite situation.
ideally local dev would also be a postgresql container, this would make data migration pretty trivial.

@northdpole northdpole self-assigned this Apr 3, 2022
@northdpole northdpole added the P1 High Priority label Apr 3, 2022
@northdpole northdpole linked a pull request Apr 10, 2022 that will close this issue
Open
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@northdpole northdpole

Labels
P1 High Priority
Projects
None yet
Milestone
Data health checks
Development

Successfully merging a pull request may close this issue.

Data equivalency OWASP/OpenCRE
1 participant
@northdpole