docs fixes

Author: maltesander

docs/modules/demos/pages/argo-cd-git-ops.adoc

@@ -56,6 +56,17 @@ This demo consists of multiple parts:
 
 TODO: arch overview image
 
+== Sealed Secrets
+
+When managing all resources and configs via Git, deploying sensitive properties like certificates or credentials via Git becomes a problem.
+
+There are multiple solutions like Hashicorp or Bitwarden, which heavily depend on the infrastructure already available.
+
+For the sake of this demo, {sealed-secrets}[Bitnami's Sealed Secrets] are utilized. 
+Sensitive data is encrypted as a `SealedSecret` before commiting to the Git repository, synced via ArgoCD and decrypted by the Sealed Secrets controller into a standard Kubernetes `Secret`.
+
+This way, everything will be stored and managed in Git.
+
 == ArgoCD UI
 
 ArgoCD will be the first product that is deployed in this Demo. Once the pods are ready, you can port-forward the argocd-server in order to access the Web UI.
@@ -67,21 +78,10 @@ kubectl --namespace argo-cd port-forward service/argocd-server 8443:https
 
 In your browser, go to `https://localhost:8443` and login with username `admin` and password `adminadmin`.
 
-NOTE: There will be an initial warning from the Browser that this site is insecure due to self-signed certificates. This can be ignored in this case.
+NOTE: There will be an initial warning from the Browser, that this site is insecure due to self-signed certificates. This can be ignored in this case.
 
 TODO: screenshots
 
-== Sealed Secrets
-
-When managing all resources and configs via Git, deploying sensitive properties like certificates or credentials via Git becomes a problem.
-
-There are multiple solutions like Hashicorp or Bitwarden, which heavily depend on the infrastructure already available.
-
-For the sake of this demo, {sealed-secrets}[Bitnami's Sealed Secrets] are utilized. 
-Sensitive data is encrypted as a `SealedSecret` before commiting to the Git repository, synced via ArgoCD and decrypted by the Sealed Secrets controller into a standard Kubernetes `Secret`.
-
-This way, everything will be stored and managed in Git.
-
 == Stackable operators
 
 The Stackable operators are deployed via ArgoCD using the Stackable Helm charts and an ArgoCD {argo-cd-applicationset}[`ApplicationSet`].
@@ -90,8 +90,7 @@ using different versions and Git sources (repository & branch) as well as the po
 
 NOTE: This demo does not use a multi cluster environment for the sake of simplicity. 
 
-[source,console]
-----
+[source,yaml]
 ---
 apiVersion: argoproj.io/v1alpha1
 kind: ApplicationSet
@@ -100,39 +99,15 @@ metadata:
 spec:
   generators:
     - matrix:
-        generators:licationSet`.
-** Spin up requirements like Minio and Postgres as `Application`.  
-** Deploy Stackable Airflow manifests in their respective `Projects`.
-** DAGs are synced via Airflow gitsync, not ArgoCD.
-** Airflow uses the Kubernetes executor and write its logs to S3 / Minio.
-** DAGs can be started manually in the Airflow webserver UI
-
-TODO: arch overview image
-
-== ArgoCD UI
-
-ArgoCD will be the first product that is deployed in this Demo. Once the pods are ready, you can port-forward the argocd-server in order to access the Web UI.
-
+        generators:
           - list:
               elements:
                 - operator: commons
                 - operator: listener
                 - operator: secret
                 - operator: airflow
                 - operator: druid
-                - operator: hbaselicationSet`.
-** Spin up requirements like Minio and Postgres as `Application`.  
-** Deploy Stackable Airflow manifests in their respective `Projects`.
-** DAGs are synced via Airflow gitsync, not ArgoCD.
-** Airflow uses the Kubernetes executor and write its logs to S3 / Minio.
-** DAGs can be started manually in the Airflow webserver UI
-
-TODO: arch overview image
-
-== ArgoCD UI
-
-ArgoCD will be the first product that is deployed in this Demo. Once the pods are ready, you can port-forward the argocd-server in order to access the Web UI.
-
+                - operator: hbase
                 - operator: hdfs
                 - operator: hive
                 - operator: kafka
@@ -175,7 +150,7 @@ ArgoCD will be the first product that is deployed in this Demo. Once the pods ar
 
 The `matrix.generators.list[].elements[]` will create a union of parameters that may be used in the `ApplicationSet` template as follows:
 
-[source,console]
+[source,yaml]
 ----
 # [...]
 template:
@@ -212,7 +187,7 @@ template:
 
 The templated version for e.g. the parameters `operator=zookeeper`, `server=https://kubernetes.default.svc` and `targetRevision=25.7.0` will result in the following template:
 
-[source,console]
+[source,yaml]
 ----
 # [...]
 template:

stacks/argo-cd-git-ops/applications/sealed-secrets.yaml

@@ -14,9 +14,10 @@ spec:
         releaseName: sealed-secrets-controller
         valuesObject:
           secretName: sealed-secrets-key
-    # TODO: This should be parameterized with customGitUrl and customGitBranch
+    # TODO: This should be parameterized with customGitUrl and customGitBranch parameters.
     # Currently these parameters are defined in the demo-v2.yaml and are
     # not picked up in the stack - What to do?
+    # TODO: adapt to main / 25.7
     - repoURL: https://github.com/stackabletech/demos/
       targetRevision: spike/argocd-demo
       path: stacks/argo-cd-git-ops/secrets/