Design: Introduce the ability to compare between two consecutive State file versions

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Problem Statement

When an organisation is managing their infrastructure with Terraform, one of the main use cases users navigate to the Terraform State page, and specifically to the versions, is to troubleshoot infrastructure problems that occurred after a change. They can identify the cause of the problem by backtracking to the Terraform code that changed, however, this might be a time consuming and frustrating experience. We want to improve the way they Troubleshoot Terraform from GitLab.

Personas

Proposal

000_State_page-Changes_tab-no_data

000_State_page-Changes-MVC

001_State_page-Changes-MVC

002_State_page-Changes-MVC

003_State_page-Changes-MVC

004_State_page-Changes-MVC

Further details

  • Design the diff based on the MR diff.
  • Add a summary of the number of resources that changed (modified, added, deleted) between the versions that are being compared (Issue: #281829 (closed))
  • For the version selection consider adding richer information besides just the commit ID (commit message, date, user who made the change).
  • Enable the selection of any older version to compare (issue:#281933).

Files

Changes tab design - Figma file

Terraform managed State - Figma file

Edited by 🤖 GitLab Bot 🤖