Skip to content

Introduce actions in the Terraform State listing for Project Maintainers

Release notes

https://docs.gitlab.com/ee/user/infrastructure/terraform_state.html#managing-state-files

If you use GitLab Managed Terraform states until now you had to use the API for various management tasks around state files, like releasing a state lock. Together with providing a listing of GitLab Managed State files, from now on you GitLab provides basic state management through its UI. You can lock or unlock a state file, download the state JSON or remove the state altogether. While we believe that these features make GitLab Managed State ready for serious production use cases, we plan to provide even more insight in future iterations. If you would like to collaborate, you can provide feedback in the related epic.

User experience goal

Allow the project maintainers perform basic actions on the Terraform State files from the state file listing without having to navigate to the State file details page.

Proposal

Make the most important actions available for each row. As we have many design patterns for row actions we need to review with the design team and decide the most appropriate pattern until there is a formal Pajamas guideline.

  • Add a download action
  • Add a lock action
  • Add a remove action

000_Terraform_State_listing_actions

001_Terraform_State_listing-_actions_expanded

002_Terraform_State_listing-actions-remove__1

003_Terraform_State_listing-actions-remove__2

004_Terraform_State_listing-actions-remove_locked__1___1

005_Terraform_State_listing-actions-remove_locked__2

Further details

  • The "Download" action should follow the download pattern in GitLab.
  • The actions are visible only to Project maintainers.

Permissions and Security

The list actions are visible and available only to Project maintainers.

Links / references

Figma file

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.

Edited by 🤖 GitLab Bot 🤖