Before a Terraform change that opens a new peering path for emergen…

Question

Before a Terraform change that opens a new peering path for emergency services merges, a second city engineer must examine the diff. What source-control practice is this?

Accepted Answer

Code review as a quality and security gate before merge. — Two pairs of eyes beat one hurried merge—especially when the change is a network peering for 911 systems. Code review is the seatbelt: catch the bad route, secret, or typo before it hits main. Force-pushing solo is how outages get a head start.

Answer

Deleting the remote repository after every successful apply.

Answer

Skipping peer input whenever the change touches only comments.

Answer

Force-pushing directly to production main to save calendar time.

Before a Terraform change that opens a new peering path for emergency services merges, a second city engineer must examine the diff. What source-control practice is this?

Short Explanation

Full Explanation