You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
89
89
90
-
### Remote state cleanup from local
90
+
### Remote state cleanup from local
91
91
92
92
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
93
93
- Configure same parameters as the github action, that is `AWS_PROFILE`, and leave default `name` and `region` values
Note: As said before kitchen works with workspaces, so any local test, unless you change it, will fall into the `default` workspace and will not collide with
119
+
Note: As said before kitchen works with workspaces, so any local test, unless you change it, will fall into the `default` workspace and will not collide with
120
120
Github Action tests. May collide however with other peers if they're doing similar tasks on local ;)
121
121
You can always temporary delete the `backend.tf` file on the test you're running
api error AuthorizationHeaderMalformed: The authorization header is malformed; a non-empty Access Key (AKID) must be provided in the credential."}
186
186
```
187
187
A: When the S3 bucket, where cloudtrail events are stored, is not in the same account as where the Cloud Connector workload is deployed, it requires the
0 commit comments