This repository has been archived by the owner on Feb 8, 2023. It is now read-only.
generated from 18F/.github
-
Notifications
You must be signed in to change notification settings - Fork 2
Database Transition Practices
Neil MartinsenBurrell edited this page Aug 17, 2021
·
3 revisions
Review Checklist
Does your code write to the database (create, update, edit)? If so:
- Have you checked with the legacy team about the proposed changes?
- Have you written database tests in api/spec/data that ensure the right data structures are being created in the legacy database?
- Have you reviewed the code with the appropriate legacy team members?
- Have you tested the running code in our staging environment to make sure that it works with the code in NRM's legacy development environment?
Background
The project to modernize NRM G&A involves an incremental transition, in which both the legacy system and modernized system are functioning in parallel, slowly moving functionality toward the modernized system.
In order to ensure that both systems work well and continue to support the Forest Service's business needs, all code that writes to the database must be thoroughly tested to ensure that the modernized system respects the data needs of the legacy database.
NRM-Grants-Agreements Path Analysis
Home
How we work
Tech
- Platform and Technologies
- Architecture diagram
- Architecture Decision Records (GitHub)
- Release Engineering Process
Design
- Our design approach
- Visual styles
- Design tools
- Timeline of design activities
- Design debt
- Additional design resources
User research