Iter1: Show Terraform state details and previous versions

Release notes

Problem to solve

This is the first iteration of #262916

This is the first step to make GitLab the tool of choice for troubleshooting Terraform by providing all the information and links to the code changes that updated the State file historically.

Intended users

• Cameron (Compliance Manager)
• Devon (DevOps Engineer)
• Allison (Application Ops)
• Priyanka (Platform Engineer)

User experience goal

The user can see an overview of a given state, including its versions.

Proposal

Further details

Tasks to complete:

• Add GraphQL ability to query single state
• Add GraphQL ability to query the list of versions
• Connect GraphQL Terraform::StateType to commit details. (currently the state can access the Job and commit sha. Other commit information, like commit message, is missing)
• Investigate TF version data. Is this information available? If so, add to GraphQL. If not, this will likely require additional tasks.
• Investigate Resources data. Is this information available? If so, add to GraphQL. If not, this will likely require additional tasks.
• Investigate latest_version size. Is this information available? If so, add to GraphQL. If not, this will likely require additional tasks.
• Investigate state lineage. Is this information available? If so, add to GraphQL. If not, this will likely require additional tasks.
• Create route/view/controller/vue setup to display information (This is mostly likely multiple tasks. Start with a basic view and slowly add items, like TF version, in follow-up tasks)

Permissions and Security

Documentation

Availability & Testing

What does success look like, and how can we measure that?

What is the type of buyer?

Is this a cross-stage feature?

Links / references

This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.