fix: Remove .editorconfig checker issues

.github/workflows/pr.yaml

@@ -42,4 +42,4 @@ jobs:
       - name: Editor Config
         run: |
           npm install --save-dev editorconfig-checker
-          ./node_modules/.bin/editorconfig-checker
+          ./node_modules/.bin/editorconfig-checker

.gitignore

@@ -1 +1 @@
-node_modules
+node_modules

README.md

@@ -21,4 +21,4 @@ You can configure the look and feel of the site by editing the `static/custom.cs
 
 ## Examples
 
-Any examples or files used as part of the deployment instructions are made available in the `examples` folder of this repository.
+Any examples or files used as part of the deployment instructions are made available in the `examples` folder of this repository.

dataphos-docs/Dockerfile

@@ -8,6 +8,6 @@ WORKDIR ./themes/hugo-geekdoc
 RUN npm install
 RUN npm run build
 
-WORKDIR /app 
+WORKDIR /app
 
-CMD ["server"]
+CMD ["server"]

dataphos-docs/config.toml

@@ -24,8 +24,7 @@ enableRobotsTXT = true
     endLevel = 9
 
 [taxonomies]
-   tag = "tags"
+    tag = "tags"
 
 [params]
     geekdocLogo = "brand.png"
-

dataphos-docs/content/Contact/_index.md

@@ -15,4 +15,4 @@ Welcome to the Dataphos Contact Form! We're delighted to hear from you and eager
 
 We look forward to connecting with you!
 
-{{< toc-tree >}}
+{{< toc-tree >}}

dataphos-docs/content/_index.md

@@ -17,4 +17,4 @@ At its core, **Dataphos** is an accelerator, enabling your engineers to focus on
 
 This documentation will provide a general overview of the key Dataphos use-cases, allow you to quickly set up an environment to deploy individual Dataphos components in (or help you deploy them in already-existing ones with minimal hassle), and provide in-depth information on each individual component's configuration.
 
-{{< toc-tree >}}
+{{< toc-tree >}}

dataphos-docs/content/persistor/configuration/shell.md

@@ -370,4 +370,4 @@ Below are the options to be configured if Apache Kafka is used as the destinatio
 | KRB_USERNAME              | "user"                 | N/A               |                                                      Username of the service principal                                                      | yes, if kerberos is enabled     |
 
 {{</ tab >}}
-{{</ tabs >}}
+{{</ tabs >}}

dataphos-docs/content/persistor/quickstart/shell.md

@@ -321,4 +321,4 @@ By following this example, if you resubmit all the messages with the given `orig
     },
     "errors": {}
 }
-```
+```

dataphos-docs/content/persistor/usage.md

@@ -72,11 +72,10 @@ An example of a successful response is:
     "status": 200,
     "msg": "resubmission succesful",
     "summary": {
-    	"indexed_count": 2,
-    	"fetched_count": 2,
-    	"deserialized_count": 2,
-    	"published_count": 2
-
+        "indexed_count": 2,
+        "fetched_count": 2,
+        "deserialized_count": 2,
+        "published_count": 2
     }
 }
 ``` 

dataphos-docs/content/publisher/_index.md

@@ -8,4 +8,4 @@ The Publisher is developed for running a constant flow of ready to digest data p
 
 
 
-{{< toc-tree >}}
+{{< toc-tree >}}

dataphos-docs/content/publisher/configuration/_index.md

@@ -128,4 +128,4 @@ In order to integrate Publisher with the [Dataphos Schema Registry](/schema_regi
 
 ```bash
 kubectl -n dataphos get svc schema-registry-svc
-```
+```

dataphos-docs/content/publisher/usage.md

@@ -111,7 +111,7 @@ The Destination configuration YAML file is used to define the details regarding
 |destinationName   |String   |	Name of the destination configuration. This value needs to be unique upon a single Publisher deployment. Specifying the existing destination name when creating a new destination resource will result in failure. Also, this name cannot be empty, this is the unique identifier of an existing and active destination configuration in the database.  |Yes   |
 |destinationType   |String   |Destination type represents the type of destination service that destination configuration will be using. Supported destination types: PubSub, Solace, Kafka, Azure (ServiceBus from version 0.5.1), NatsCore, NatsJetStream.    | Yes |
 |parameters*   |Key-value map   | The values specific for some messaging platforms can be defined in the form of a key: value map.  |Yes   |
- {{< /tab >}}
+{{< /tab >}}
 
 {{< tab "Google PubSub" >}} 
 
@@ -394,4 +394,4 @@ Below is the screen you will be greeted with after first logging into the Publis
 
 **WEB CLI** - update and process YAML files to update sources, destinations, configuration. First, add source YAML, then destination and then instance. You can add, update and delete your configuration. 
 
-![](/webcli.PNG)
+![](/webcli.PNG)

dataphos-docs/content/referenced scripts/YAML examples/_index.md

@@ -4,4 +4,4 @@ draft: false
 weight: 3
 geekdocCollapseSection: true
 ---
-{{< toc-tree >}}
+{{< toc-tree >}}

dataphos-docs/content/referenced scripts/_index.md

@@ -6,4 +6,4 @@ weight: 5
 
 Scripts for deploying Dataphos.
 
-{{< toc-tree >}}
+{{< toc-tree >}}

dataphos-docs/content/referenced scripts/deployment scripts/_index.md

@@ -4,4 +4,4 @@ draft: false
 weight: 3
 geekdocCollapseSection: true
 ---
-{{< toc-tree >}}
+{{< toc-tree >}}

dataphos-docs/content/referenced scripts/deployment scripts/persistor.md

@@ -12,7 +12,7 @@ draft: false
 #!/bin/bash
 if [ $# -ne 12 ]; then
         echo "please specify all required variables"
-		exit 1
+    exit 1
 fi
 client_id=$1
 client_secret=$2
@@ -333,7 +333,7 @@ EOF
 #!/bin/bash
 if [ $# -ne 8 ]; then
         echo "please specify all required variables"
-		exit 1
+    exit 1
 fi
 project_id=$1
 persistor_topic=$2
@@ -676,7 +676,7 @@ EOF
 #!/bin/bash
 if [ $# -ne 12 ]; then
         echo "please specify all required variables"
-		exit 1
+    exit 1
 fi
 client_id=$1
 client_secret=$2
@@ -1012,7 +1012,7 @@ EOF
 #!/bin/bash
 if [ $# -ne 10 ]; then
         echo "please specify all required variables"
-		exit 1
+    exit 1
 fi
 project_id=$1
 persistor_kafka_address=$2

dataphos-docs/content/referenced scripts/deployment scripts/prometheus.md

@@ -12,7 +12,7 @@ Deployment script for the Prometheus server for gathering the metrics and monito
 #!/bin/bash
 if [ $# -ne 1 ]; then
         echo "please specify all required variables"
-		exit 1
+    exit 1
 fi
 
 namespace=$1

dataphos-docs/content/referenced scripts/deployment scripts/schemaregistry.md

@@ -12,7 +12,7 @@ draft: false
 
 if [ $# -ne 2 ]; then
         echo "please specify all required variables"
-		exit 1
+    exit 1
 fi
 
 namespace=$1
@@ -249,7 +249,7 @@ EOF
 
 if [ $# -ne 1 ]; then
         echo "please specify all required variables"
-		exit 1
+    exit 1
 fi
 
 namespace=$1
@@ -485,7 +485,7 @@ EOF
 
 if [ $# -ne 8 ]; then
         echo "please specify all required variables"
-		exit 1
+    exit 1
 fi
 
 namespace=$1
@@ -582,7 +582,7 @@ EOF
 }
 
 if [ "$message_type" = "csv" ]; then
-   deploy_csv_validator
+    deploy_csv_validator
 elif [ "$message_type" = "xml" ]; then
     deploy_xml_validator
 fi
@@ -673,7 +673,7 @@ EOF
 
 if [ $# -ne 2 ]; then
         echo "please specify all required variables"
-		exit 1
+    exit 1
 fi
 
 namespace=$1
@@ -764,7 +764,7 @@ EOF
 }
 
 if [ "$message_type" = "csv" ]; then
-   delete_csv_validator
+    delete_csv_validator
 elif [ "$message_type" = "xml" ]; then
     delete_xml_validator
 fi
@@ -855,7 +855,7 @@ EOF
 
 if [ $# -ne 8 ]; then
         echo "please specify all required variables"
-		exit 1
+    exit 1
 fi
 
 namespace=$1
@@ -952,7 +952,7 @@ EOF
 }
 
 if [ "$message_type" = "csv" ]; then
-   deploy_csv_validator
+    deploy_csv_validator
 elif [ "$message_type" = "xml" ]; then
     deploy_xml_validator
 fi
@@ -1054,7 +1054,7 @@ EOF
 
 if [ $# -ne 2 ]; then
         echo "please specify all required variables"
-		exit 1
+    exit 1
 fi
 
 namespace=$1
@@ -1146,7 +1146,7 @@ EOF
 }
 
 if [ "$message_type" = "csv" ]; then
-   delete_csv_validator
+    delete_csv_validator
 elif [ "$message_type" = "xml" ]; then
     delete_xml_validator
 fi
@@ -1248,7 +1248,7 @@ EOF
 
 if [ $# -ne 7 ]; then
         echo "please specify all required variables"
-		exit 1
+    exit 1
 fi
 
 namespace=$1
@@ -1348,7 +1348,7 @@ EOF
 }
 
 if [ "$message_type" = "csv" ]; then
-   deploy_csv_validator
+    deploy_csv_validator
 elif [ "$message_type" = "xml" ]; then
     deploy_xml_validator
 fi
@@ -1449,7 +1449,7 @@ EOF
 
 if [ $# -ne 2 ]; then
         echo "please specify all required variables"
-		exit 1
+    exit 1
 fi
 
 namespace=$1
@@ -1541,7 +1541,7 @@ EOF
 }
 
 if [ "$message_type" = "csv" ]; then
-   delete_csv_validator
+    delete_csv_validator
 elif [ "$message_type" = "xml" ]; then
     delete_xml_validator
 fi
@@ -1642,7 +1642,7 @@ EOF
 
 if [ $# -ne 8 ]; then
         echo "please specify all required variables"
-		exit 1
+    exit 1
 fi
 
 namespace=$1
@@ -1739,7 +1739,7 @@ EOF
 }
 
 if [ "$message_type" = "csv" ]; then
-   deploy_csv_validator
+    deploy_csv_validator
 elif [ "$message_type" = "xml" ]; then
     deploy_xml_validator
 fi
@@ -1831,7 +1831,7 @@ EOF
 
 if [ $# -ne 2 ]; then
         echo "please specify all required variables"
-		exit 1
+    exit 1
 fi
 
 namespace=$1
@@ -1922,7 +1922,7 @@ EOF
 }
 
 if [ "$message_type" = "csv" ]; then
-   delete_csv_validator
+    delete_csv_validator
 elif [ "$message_type" = "xml" ]; then
     delete_xml_validator
 fi

dataphos-docs/content/schema_registry/_index.md

@@ -6,4 +6,4 @@ weight: 1
 
 The Schema Registry is a one-stop solution for registering schemas for serialized data running through your streaming infrastructure and validating them in-flight without changing a single line of existing code.
 
-{{< toc-tree >}}
+{{< toc-tree >}}

dataphos-docs/content/schema_registry/configuration/helm.md

@@ -82,4 +82,4 @@ the release, explicitly referencing brokers defined in the previous section.
 | validator.VAL_ID.deadletterTopic      | string | The topic INVALID messages are sent TO.                                                                                               |                                      |
 | validator.VAL_ID.replicas             | string | The number of replicas of a given validator instance to pull/process messages simultaneously.                                         |                                      |
 | validator.VAL_ID.serviceAccountSecret | string | The reference to a secret that contains a `key.json` key and the contents of a Google Service Account JSON file as its contents.      | `brokers.BROKER_ID.type` == `pubsub` |
-| validator.VAL_ID.serviceAccountKey    | string | A Google Service Account private key in JSON format, base64 encoded. Used to create a new `serviceAccountSecret` secret, if provided. | `brokers.BROKER_ID.type` == `pubsub` |
+| validator.VAL_ID.serviceAccountKey    | string | A Google Service Account private key in JSON format, base64 encoded. Used to create a new `serviceAccountSecret` secret, if provided. | `brokers.BROKER_ID.type` == `pubsub` |

dataphos-docs/content/schema_registry/quickstart/helm.md

@@ -178,4 +178,4 @@ helm install schema-validator ./dataphos-schema-validator
 
 This would cause the `values.yaml` file to be read from the root directory of the `dataphos-schema-validator` folder. The `--values` flag may be passed in the call to override this behavior.
 
-You can also add a `--dry-run` flag that will simply generate the Kubernetes manifests and check if they are valid (note that this requires `kubectl` to be configured against an actual cluster). For general linting of the Helm templates, run `helm lint`. 
+You can also add a `--dry-run` flag that will simply generate the Kubernetes manifests and check if they are valid (note that this requires `kubectl` to be configured against an actual cluster). For general linting of the Helm templates, run `helm lint`.

dataphos-docs/content/schema_registry/quickstart/pulumi.md

@@ -158,4 +158,4 @@ Destroy your infrastructure changes:
 $ pulumi destroy
 ```
 
-Following the deployment, the Schema Registry components will begin automatically pulling data from the configured topic and delivering it to the target storage destination.
+Following the deployment, the Schema Registry components will begin automatically pulling data from the configured topic and delivering it to the target storage destination.

dataphos-docs/layouts/partials/head/custom.html

@@ -1,2 +1,2 @@
 <!-- You can add custom elements to the page header here. -->
-{{ template "_internal/google_analytics.html" . }}
+{{ template "_internal/google_analytics.html" . }}

dataphos-docs/layouts/partials/site-footer.html

@@ -43,4 +43,3 @@
       {{ end }}
     </nav>
   </footer>
-