Invalidate a plan when the state changes
Problem Statement
As a DevOps engineer, in order to review a valid plan, I would like to avoid invalid plans in merge requests.
Some Terraform backend provide locking the state if it might just be changed. As the terraform backend is not integrated with GitLab, we don't know about situation when a plan become invalid.
If the user uses the GitLab Terraform backend, then we should be able to invalidate the plans.
Reach
3.0 = Significant reach (~25% to ~50%).
Based on the market penetration of IaC tools, this might benefit a significant portion of our on-prem users.
Impact
1.0 = Medium impact 0.5 = Low impact
Not having this feature causes some inconvenience for the engineers doing Terraform code reviews. By the time the review is run, its planned changes might be outdated. Still, we think that this feature makes our Terraform offering really competitive and provides an integrated experience that GitLab advocates for.
Confidence
We would like to learn more about how our customers do state locking or get around it, to increase confidence.
50% = Low confidence
Effort
TBD, this issue builds on other issues seen in the related issues list.