Skip to content

Commit d624c81

Browse files
author
iru
authored
docs: howto unlock tf state
1 parent ce2df7e commit d624c81

File tree

1 file changed

+13
-4
lines changed

1 file changed

+13
-4
lines changed

CONTRIBUTE.md

Lines changed: 13 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -59,10 +59,6 @@ We're using **pre-commit** | https://pre-commit.com
5959
<!-- END OF PRE-COMMIT-TERRAFORM DOCS HOOK -->
6060
```
6161

62-
- If pre-commit fails on Github but not on your local, try cleaning-up `terraform` files with
63-
`./resources/terraform-clean.sh` script
64-
65-
6662
## 2. Check::Integration tests
6763

6864
Final user validation. Checks that the snippets for the usage, stated in the official Sysdig Terraform Registry, are working correctly.
@@ -87,6 +83,19 @@ Implemented vía **Terraform Kitchen** | https://newcontext-oss.github.io/kitche
8783

8884
Because CI/CD sometimes fail, we setup the Terraform state to be handled in backend (s3+dynamo) within the Sysdig AWS backend (sysdig-test-account).
8985

86+
#### Howto unlock terraform backend
87+
88+
```
89+
# go to the specific test ex.:
90+
cd test/fixtures/single-subscription
91+
92+
# unlock kitchetn state
93+
terraform init
94+
terraform workspace list
95+
terraform workspace select kitchen-terraform-WORKSPACE_NAME
96+
terraform force-unlock LOCK_ID
97+
```
98+
9099
### Remote state cleanup from local
91100

92101
In case you need to handle terraform backend state from failing kitchen tests, some guidance for using the `backend.tf` remote state manifest, present on each test

0 commit comments

Comments
 (0)