@yrimal
There's a lot of people who access our Postgres Server. I want to make sure all the use-cases still function or can be adequately substituted while this is re-architected in a different network.

Can you describe what you are doing when you access the server (crons, scripts) related to postgres, and what's typical use for partners, since I see a lot of partner type logins present?

Thanks

Hi @Hareet ,
For impact monitoring, impact team creates certain views and functions on each database. It's not always the same query for all database so we can't containerize it. Once impact functions have been installed on these databases, we've a dblink connection set from dwh_impact database that queries every databases to pull updated data every other night.

Apart from this, when there's a need to query database for other purposes, then also we need to access those databases.

For partner users, only some (probably just lg) have direct access to the database. But, at least one account will still need access from klipfolio for partner facing dashboards. If things are not clear, I can talk over call as well.

Testing:

• Be able docker-compose medic-os container or arch v3 containers (docker-compose)
• Launch couch2pg + postgres containers after medic-os is initiliazed, and verify data is inserted to postgres
• Entrypoints work in restarts, crashes and initial setup

We have labeled this ticket as 5 points for SRE Sprint 2

Unable to share medic-infrastructure labels with this repo.

completed!