ci: lint

Author: iru

use-cases/README.md

@@ -5,9 +5,9 @@
 ### Feature Summary
 
 | Cloud | Single Setup | Organizational Setup | Event Source | Compute Deployment Options | Sysdig Role Setup | Image Scanning Options | Spawned Scanning Service
-| -- | --- | --- | --- | --- | --- | --- | --- | 
-| AWS | Account | Organization with member accounts | Cloudtrail | K8S `-k8s`, ECS `-ecs`, AppRunner `-apprunner` | IAM Role with Trusted Identity | ECS deployed images,<br/>ECR, Public Repositories | Codebuild project | 
-| GCP | Project | Organization with member projects | Project/Organization Sink,<br/> GCR PubSub Topic | K8S `-k8s`, CloudRun | Workload Identity Federation | CloudRun deployed images,<br/>GCR, Public Repositories |Cloudbuild task | 
+| -- | --- | --- | --- | --- | --- | --- | --- |
+| AWS | Account | Organization with member accounts | Cloudtrail | K8S `-k8s`, ECS `-ecs`, AppRunner `-apprunner` | IAM Role with Trusted Identity | ECS deployed images,<br/>ECR, Public Repositories | Codebuild project |
+| GCP | Project | Organization with member projects | Project/Organization Sink,<br/> GCR PubSub Topic | K8S `-k8s`, CloudRun | Workload Identity Federation | CloudRun deployed images,<br/>GCR, Public Repositories |Cloudbuild task |
 | Azure | Subscription | Tenant subscriptions| EventHub, Eventgrid | K8S `-k8s`, AzureContainerInstances (ACI) | Azure Lighthouse | ACI deployed images,<br/> ACR, Public Repositories | ACR Task |
 
 
@@ -57,7 +57,7 @@ For [complete feature installation](https://docs.sysdig.com/en/docs/sysdig-secur
 
 With both examples `single` and `org`, you can customize the desired features to de deployed with the `deploy_*` input vars to avoid deploying more than wanted.
 
-### Unified Compliance 
+### Unified Compliance
 
 If you just want [CIS Unified Compliance Benchmarks](https://docs.sysdig.com/en/docs/sysdig-secure/posture/compliance/compliance-unified-/)
 see [Compliance role-only deployment with Terraform](https://docs.sysdig.com/en/docs/installation/sysdig-secure-for-cloud/deploy-sysdig-secure-for-cloud-agentless/)

use-cases/manual-compliance.md

@@ -5,7 +5,7 @@ To enable [CSPM (Compliance)](https://docs.sysdig.com/en/docs/sysdig-secure/post
 - An `account` representing the AWS account for which you want to enable CSPM
 - A trust-relationship `component` that represents the IAM Role in your AWS account
 - A CSPM `feature` that indicates CSPM scans should be run against this account
- 
+
 
 ## Guidelines
 

use-cases/manual-org-three-way.md

@@ -42,7 +42,7 @@ This setup will provide the following [Sysdig Secure for Cloud](https://docs.sys
 
 - AWS member account for Compliance
 
-  - Sysdig Compliance Role:`aws:SecurityAudit policy`.  
+  - Sysdig Compliance Role:`aws:SecurityAudit policy`.
 
     For more information, see [Creating IAM roles](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create.html).
 

use-cases/multiple-accounts-k8s-threat.md

@@ -51,7 +51,7 @@ The ingestor processes a single SQS AWS queue with the events reported from:
 1. Define different **AWS providers**:
 
     WIP.
-     
+
     - We need to know the account where Sysdig Secure for cloud workload will be deployed
     - And the accounts where the cloudtrail-S3 bucket(s) will be
     <!--
@@ -66,7 +66,7 @@ The ingestor processes a single SQS AWS queue with the events reported from:
       region = "<REGION>"
       ...
       }
-      
+
       provider "aws" {
       alias = "sfc"
       region = "<REGION>"
@@ -158,72 +158,72 @@ The ingestor processes a single SQS AWS queue with the events reported from:
 
      ```yaml
      resource "helm_release" "cloud_connector" {
-     
+
        provider = helm
-     
+
        name = "cloud-connector"
-     
+
        repository = "https://charts.sysdig.com"
        chart      = "cloud-connector"
-     
+
        create_namespace = true
        namespace        = "sysdig"
-     
+
        set {
          name  = "image.pullPolicy"
          value = "Always"
        }
-     
+
        set {
          name  = "sysdig.url"
          value =  "<sysdig_secure_url>"
        }
-     
+
        set_sensitive {
          name  = "sysdig.secureAPIToken"
          value = "<SYSDIG_SECURE_API_TOKEN>"
        }
-     
+
        set_sensitive {
          name  = "aws.accessKeyId"
          value = "<AWS_ACCESS_KEY>"
        }
-     
+
        set_sensitive {
          name  = "aws.secretAccessKey"
          value = "<AWS_SECRET_ACCESS_KEY>"
        }
-     
+
        set {
          name  = "aws.region"
          value = "<REGION>"
        }
-     
+
        set {
          name  = "nodeSelector.<NODE_SELECTOR_LABEL>"
          value = "<NODE_SELECTOR_LABEL_VALUE>"
        }
-     
+
        set {
          name  = "tolerations[0].key"
          value = "<TOLERATION_KEY>"
        }
-     
+
        set {
          name  = "tolerations[0].operator"
          value = "<TOLERATION_OPERATOR>"
        }
-     
+
        set {
          name  = "tolerations[0].value"
          value = "<TOLERATION_VALUE>"
        }
-     
+
        set {
          name  = "tolerations[0].effect"
          value = "<TOLERATION_EFFECT>"
        }
-     
+
        values = [
          <<CONFIG
      logging: info

use-cases/org-three-way-ecs.md

@@ -2,7 +2,7 @@
 
 ## Overview
 
-This use case covers securing a multi-account AWS environment with workload on ECS, typically created with the [AWS ControlTower landing zone](https://aws.amazon.com/controltower/features/). 
+This use case covers securing a multi-account AWS environment with workload on ECS, typically created with the [AWS ControlTower landing zone](https://aws.amazon.com/controltower/features/).
 
 The guidelines are terraform-based. For instruction on setting up Secure for Cloud manually, see [Manual Organizational Setup - Three-Way Cross-Account](./manual-org-three-way.md).