Update contactview_metadata to be compatible with configurable contact hierarchies

[1yuv]

Current version of contactview_metadata was last updated on 2018. Since then, we've added configurable hierarchy to CHT-Core and for most of the partners using latest version of CHT-Core, contact_type field is also important.

Whenever couch2pg runs, it creates contactview_metadata, so we should ensure that we're creating required field in contactview_metadata instead of partners/tech leads requiring to drop and recreate this mat view again.

[1yuv]

Hi @latin-panda ,
Current version of script doesn't reassign owner to full_access, hence that work needs to be taken care manually most of the time.

Can you reassign the owner for each object after they're created to full_access as well?
The syntax is :

ALTER [OBJECT_TYPE] [OBJECT_NAME] OWNER TO full_access;

[nomulex]

full_access is a medic specific role, I am not sure if this is wise to put it in the code that will be used by the cht community.

[1yuv]

I also thought about that. But, this repo (medic-couch2pg) is medic specific instance and I think we should put that. But not put REASSIGN on our public repo.

[latin-panda]

Hey guys, I've verified and effectively this repo is designed to support all CHT deployments, even self hosted. So we should not hardcode Medic-specific roles, but we can include this as a separate script that runs in demand, I've raised a ticket to address this next.

[newtewt]

I've tested this in my local setup. By tearing down the current medic-couch2pg container and then spinning up one from this branch. The materialized view sql statement is updated in the properties and the query returns the screenshot below. I am not sure how our Prod upgrade process works for medic-couch2pg and if it's worth verifying during this to ensure it doesn't break.

[newtewt]

[newtewt]

@latin-panda this is ready to merge.

[latin-panda]

PR has been merged.