Run both apps on the same database

[pbastia]

User Story

As a developer, I want 2 separate Django apps using the same database so that both registration and reporting apps can live side by side

Description:

Django by default writes to tables in the public schema of the database. It is currently unknown if there are any side-effects to having 2 apps side by side using the same database.

This card is about exploring what the best way of doing this would be, and what are industry best practices around solving this issue.

Acceptance Criteria:

Given I am a developer When I deploy the reporting app's database in the same database as the registration app's Then there are no side-effects And everything works as intended

Development Checklist:

• [ ] Investigate feasibility (there's an interesting resource here https://books.agiliq.com/projects/django-multi-tenant/en/latest/shared-database-isolated-schema.html)
• [ ] Database vs. database cluster: Issues will only arise if we use the same database. We might want to host 2 databases on the same Crunchy cluster
• [ ] Configure helm values to use existing deployed database
• [ ] Have a meeting with all devs/architects
• [ ] Meets the DOD

Definition of Ready (Note: If any of these points are not applicable, mark N/A)

• [ ] User story is included
• [ ] User role and type are identified
• [ ] Acceptance criteria are included
• [ ] Wireframes are included (if required)
• [ ] Design / Solution is accepted by Product Owner
• [ ] Dependencies are identified (technical, business, regulatory/policy)
• [ ] Story has been estimated (under 13 pts)

Definition of Done (Note: If any of these points are not applicable, mark N/A)

• [ ] Acceptance criteria are tested by the CI pipeline
• [ ] UI meets accessibility requirements
• [ ] Configuration changes are documented, documentation and designs are updated
• [ ] Passes code peer-review
• [ ] Passes QA of Acceptance Criteria with verification in Dev and Test
• [ ] Ticket is ready to be merged to main branch
• [ ] Can be demoed in Sprint Review
• [ ] Bugs or future work cards are identified and created
• [ ] Reviewed and approved by Product Owner

Notes:

-

[pbastia]

@dleard tagging you here in case you have wisdom to share

[pbastia]

closing this, as we're deploying in the same database