Design drift map of a travel-booking site

Views in this map

1. 1
   Approved designApproved in March: private endpoints, a geo-replica in Central US, a WAF that blocks.
2. 2
   In TerraformTerraform lacks the geo-replica and Prevention mode, and adds a debug account.
3. 3
   Running in AzureThe scan: an SSH jump box, a resized database, a public Key Vault, a Function app.
4. 4
   Drift27 resources match; 3 settings changed, 4 live only, 1 design only, 1 Terraform only.
5. 5
   ReconciledAfter the fix pull requests, all match but one: the larger database, kept until Jan 31.

Approved design ‹ › In Terraform ‹ › Running in Azure ‹ › Drift ‹ › Reconciled

Flows to play

• ▷
  A booking, as designedOne hotel booking through the platform the board approved, from the traveller to the copy in Central US. Approved design: the request path the board signed off, from Front Door and the WAF to the geo-replica.
• ▷
  How a 2 a.m. hotfix became driftINC-4471 on Sep 28: a fix made in the portal at night, never written back, found by the scan three weeks later. Drift: from the stalled database to the jump box, the SSH rule and the scan that flags them.
• ▷
  Closing the gapsThe pull requests of Oct 20 to 28, and the one exception the board accepted. Reconciled: each fix lands on the box it changed, and the larger database keeps its exception.

The model behind it

56 records of 7 types. Every box on the map is one of them, so the filters and the record panel read the same data.

• Resources 36
• Changes 11
• Design rules 4
• People 2
• Design 1
• Terraform stack 1
• Scan 1

Filters

Drift and Owning team: pick a value and everything else fades.