Overview
As part of fb-mongod decommissioning milestones, we will implement collection level access to the database. After this policy is implemented, collections that are orphan (ownership not acknowledged by anyone) or have no usage left (based on owner's notes) will not be accessible anymore from standard backend systems.

Plan

Feb 25th, 2021 : Apply access revocation on 1pm UTC+7
Affected collection list and revocation runbook are available in this document
Contents of access limitation script can be viewed in this PR

There should be no action needed from your end as long as the data reported on the document above is accurate
In the case that you only identified afterwards that your system happened to still use any of the revoked collection, please reach out to us on #fb-mongod-decommissioning and provide the following informations :

collection name(s) which access needs to be restored
username which your system used to connect to db, e.g. : traveloka2
your engineering team's slack handle which will be documented as the Migration PIC for specified collection

The informations above will be used to create access restoration PR (example). @pda-fpr will assist in executing the script via fpr bastion.

Should you have any further questions / concerns, please let us know in #fb-mongod-decommissioning channel. Thanks !

Implementing Collection Level Access on fb-mongod