Separation of data

[tapishr]

Dod -

• Schema/db design for keeping data for now
• pipelines to sync/run jobs

[tapishr]

Gsuite id can be used as primary id for recognising orgs User schema

• our generated id
• role (em/dev)
• auth_info (json)
• aliases [array]
• current_org
• name
• photo
• code hosting site id/url
• socials (urls)
• repos [array]

[tapishr]

Commits schema

• continue with the same schema following right now

[tapishr]

Repo schema -

• id
• name
• users/aliases [array]
• repo_git_url
• metadata (json)
• auth_info

[tapishr]

Postgres schemas for all entities

[tapishr]

• [x] Create user schema, access to write to table, read from table
• [x] Create repo schema, access to write to table, read from table
• [x] Save queries in git

When user logs in -

• [x] On login, check for existing orgs/repos. If not, create new table, user specific to org from cloudrun
• [x] Push user row in table ftue
• [x] Update user table when its field values change (on every login?)
• [x] Fetch all repos for a user

[tapishr]

user table created, repo table created, access to be given, roles created. explored redis, not usable right now, development speed slow due to complex data structure.

[tapishr]

superuser role given to the website user, able to perform joins, yet to test without write permissions. Indexing permissions to be handled by admin users postgres and tapish. Created query for push table ftue and login ftue and tested login with dummy data. Need to ask about storing in git - new repo or cloudrun?

[tapishr]

PR raised with all tasks done

[avikalpg]

Change name of column profile_url to photo_url

[avikalpg]

Org schema:

1. id
2. Name
3. Members

[avikalpg]

remove org and role from users table.

[tapishr]

Created a second user table (@muskan) to store github and bitbucket specific tokens and repos

[tapishr]

Created issue 51 to track pipelines to sync data. Closing this ticket