CTHUB - New database and metabase for a certain group

[tim738745]

Title: New database and metabase for a certain group

Description: We are going to be creating multiple databases and metabases (one (db, mb) pair for each business group). This card is to create exactly one such pair.

Wireframe:

Purpose and benefit to user: We’re doing this to address concerns about data visibility/sharing, and also to overcome the metabase prohibition on cross-database queries.

Acceptance Criteria:

• [ ] Given I am a user that belongs to a certain group, when I am using metabase, I see only the data I’m supposed to see, even if I have a metabase admin role.

Development Checklist:

• [ ] Create a new database and metabase instance within the cthub cluster (devops).
• [ ] Figure out how migrations are going to work with multiple databases (see https://docs.djangoproject.com/en/5.0/topics/db/multi-db/#database-routers).
• [ ] Use Django Q to write a job that takes data from our “primary” databases (cthub, zeva, itvr, etc) and copies it to the group’s database.

Notes: This architecture assumes that the number of (database, metabase) pairs are going to be limited in number because the number of groups are going to be limited in number; if we want this to scale, we’ll have to look at something like Kafka (please see https://kafka.apache.org/)

[ArawuSamuel1]

Hey team! Please add your planning poker estimate with Zenhub @tim738745 @emi-hi