Design: Introduce a listing of Terraform State files when a Project has at least one State file
Problem to solve
This issue is for the design of how we will surface the Terraform State file in GitLab's UI (when a project has at least one state file).
User experience goal
Provide an overview of the Terraform State files included in a Project and surface information that are useful to the users without making the users navigate to the State file details page to find them. Also allow the project maintainers perform basic actions from the list for the same reason.
Proposal
Further details
- A state file might have been automatically published by GitLab's CI/CD, manually from their local environment or in other ways.
- Additionally, GitLab may not even have access to the code itself - A user could create a "Terraform States" project with no repository that does nothing but hold state details for their other projects.
- The information available in each case is different and the design needs to cover all these cases.
Permissions and Security
- The list and the information for each list item can be viewed y anyone who can access the Project.
- The list actions are visible and available only to Project maintainers.
Links / references
Edited by Maria Vrachni