GitHub Infra Issue As Tracking

Background

Recently we got a critical incident where one of our postgres in tvlk-ast-prod got accidentally deleted due to lack of communication. Post mortem: https://docs.google.com/document/d/1pixnQNAfcYMulk2JbbEDlSYH01UMRHpSHZdt3HPBqhU

We should have clear communication between all of our team members in regard of any infra changes or terraform execution in production environment. This should minimize any human errors which may cause unwanted incident.

Using GitHub Infra Issue

We would like to enforced infra issue creation before executing any infra changes in production, including AWS maintenance tasks such as restarting RDS instance, etc. Though service deployment to production is not mandatory to have infra-issue for now, but this may changed in the future.

Let us improve our process together, and let me know your ideas and inputs. Thanks team.