chore: Fix tf format and add Editor config (#11)

Author: goruha

.editorconfig

@@ -0,0 +1,32 @@
+# top-most EditorConfig file
+root = true
+
+# Unix-style newlines with a newline ending every file
+[*]
+end_of_line = lf
+insert_final_newline = true
+trim_trailing_whitespace = true
+
+# Override for Makefile
+[{Makefile,makefile,GNUmakefile}]
+indent_style = tab
+indent_size = 4
+
+[Makefile.*]
+indent_style = tab
+indent_size = 4
+
+[{*.yaml,*.yml,*.md}]
+indent_style = space
+indent_size = 2
+
+[*.sh]
+indent_style = tab
+indent_size = 2
+
+[*.{tf,tfvars,tpl,variant}]
+indent_style = space
+indent_size = 2
+
+[*.json]
+insert_final_newline = false

.github/renovate.json

@@ -3,4 +3,4 @@
   "extends": [
     "config:base"
   ]
-}
+}

.github/settings.yml

@@ -5,3 +5,4 @@ repository:
   description: 'This component deploys self-hosted GitHub Actions Runners and a Controller on an EKS cluster, using "runner scale sets"'
   homepage: https://cloudposse.com/accelerate
   topics: terraform, terraform-component
+

README.md

@@ -202,12 +202,12 @@ description: |-
   deploy to multiple regions you have 2 choices:
 
   1. Create the secrets in each region. This is the most robust approach, but requires you to create the secrets in each
-     region and keep them in sync.
+    region and keep them in sync.
   2. Create the secrets in one region and use the `ssm_region` input to specify the region where they are stored. This is
-     the easiest approach, but does add some obstacles to managing deployments during a region outage. If the region where
-     the secrets are stored goes down, there will be no impact on runners in other regions, but you will not be able to
-     deploy new runners or modify existing runners until the SSM region is restored or until you set up SSM parameters in
-     a new region.
+    the easiest approach, but does add some obstacles to managing deployments during a region outage. If the region where
+    the secrets are stored goes down, there will be no impact on runners in other regions, but you will not be able to
+    deploy new runners or modify existing runners until the SSM region is restored or until you set up SSM parameters in
+    a new region.
 
   Alternatively, you can create Kubernetes secrets outside of this component (perhaps using
   [SOPS](https://github.com/getsops/sops)) and reference them by name. We describe here how to save the secrets to SSM,

README.yaml

@@ -0,0 +1 @@
+

docs/.gitkeep

@@ -264,8 +264,8 @@ variable "descriptor_formats" {
     Describe additional descriptors to be output in the `descriptors` output map.
     Map of maps. Keys are names of descriptors. Values are maps of the form
     `{
-       format = string
-       labels = list(string)
+      format = string
+      labels = list(string)
     }`
     (Type is `any` so the map values can later be enhanced to provide additional options.)
     `format` is a Terraform format string to be passed to the `format()` function.