Enable `assumeImmutableResults` in `app/assets/javascripts/terraform/index.js`
What does this MR do?
The aim of this MR is to enable assumeImmutableResults
to enforce immutability.
Screenshots or Screencasts (strongly suggested)
The related view is Infrastructure -> Terraform
How to setup and validate locally (strongly suggested)
- Navigate to Infrastructure -> Terraform
- Create GitLab-managed Terraform state - the fastest way is to use this reference project.
- Verify the console has no related errors and the GitLab-managed Terraform states are successfully fetched.
There's a warning related to heuristic fragment matching
that will be addressed in a separate issue.
Does this MR meet the acceptance criteria?
Conformity
-
I have included changelog trailers, or none are needed. (Does this MR need a changelog?) - [-] I have added/updated documentation, or it's not needed. (Is documentation required?)
- [-] I have properly separated EE content from FOSS, or this MR is FOSS only. (Where should EE code go?)
- [-] I have added information for database reviewers in the MR description, or it's not needed. (Does this MR have database related changes?)
-
I have self-reviewed this MR per code review guidelines. -
This MR does not harm performance, or I have asked a reviewer to help assess the performance impact. (Merge request performance guidelines) -
I have followed the style guides. -
This change is backwards compatible across updates, or this does not apply.
Availability and Testing
-
I have added/updated tests following the Testing Guide, or it's not needed. (Consider all test levels. See the Test Planning Process.) -
I have tested this MR in all supported browsers, or it's not needed. -
I have informed the Infrastructure department of a default or new setting change per definition of done, or it's not needed.
Related to #338444 (closed)
Edited by Anna Vovchenko