Skip to content

Commit d184653

Browse files
author
iru
committed
doc: lint
1 parent 5af7ab3 commit d184653

File tree

2 files changed

+5
-5
lines changed

2 files changed

+5
-5
lines changed

CONTRIBUTE.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -76,7 +76,7 @@ Implemented vía **Terraform Kitchen** | https://newcontext-oss.github.io/kitche
7676
- In order to test this in your local environment use following recipee
7777
```bash
7878
terraform init -backend=false && \
79-
terraform validate && \
79+
terraform validate && \
8080
terraform plan && \
8181
read && \ # will give you time to review plan or just push enter to apply
8282
terraform apply --auto-approve
@@ -87,7 +87,7 @@ Implemented vía **Terraform Kitchen** | https://newcontext-oss.github.io/kitche
8787

8888
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).
8989

90-
### Remote state cleanup from local
90+
### Remote state cleanup from local
9191

9292
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
9393
- Configure same parameters as the github action, that is `AWS_PROFILE`, and leave default `name` and `region` values
@@ -116,7 +116,7 @@ $ bundle exec kitchen tests
116116
$ bundle exec kitchen test "single-account-k8s-aws"
117117
```
118118

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
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
120120
Github Action tests. May collide however with other peers if they're doing similar tasks on local ;)
121121
You can always temporary delete the `backend.tf` file on the test you're running
122122

README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -180,8 +180,8 @@ A: Make sure you installed both [cloud-bench](https://github.com/sysdiglabs/terr
180180
### Q: I get 400 api error AuthorizationHeaderMalformed on the Sysdig workload ECS Task
181181

182182
```text
183-
error while receiving the messages: error retrieving from S3 bucket=crit-start-trail: operation error S3: GetObject,
184-
https response error StatusCode: 400, RequestID: ***, HostID: ***,
183+
error while receiving the messages: error retrieving from S3 bucket=crit-start-trail: operation error S3: GetObject,
184+
https response error StatusCode: 400, RequestID: ***, HostID: ***,
185185
api error AuthorizationHeaderMalformed: The authorization header is malformed; a non-empty Access Key (AKID) must be provided in the credential."}
186186
```
187187
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

Comments
 (0)