Standardize Receiver config documentation in Keybase
Problem statement
Receiver configuration documentation, most importantly transport information, is stored in keybase. Each receiving organization has a folder containing the documentation. That documentation is maintained by various engineers but has never been standardized so retrieving that needed information is confusing and time consuming.
What you need to know
Keybase folder locations:
Acceptance criteria
- [ ] All documentation is uniform
- [ ] Unneeded documentation is removed
- [ ] Process for updating documentation is created and added to new engineer onboarding packet
Does this stuff need to be in Keybase and the database and Azure?
TBD based on future Engagement Engr Sync
Check in with DevOps to see if we can still use Key Base
Mikaelah to check in on status with Jeremy to see what they recommend using as a replacement for Keybase?
Response from Jeremy: Don't use Keybase anymore for storing credentials.
Credentials should be stored in Sharepoint and documents containing credentials should be labeled as "Restricted Use". If needed, use Recipients only and ensure that all onboarding engineers are recipients.