WIP: delay applications to a non-default, later sync-wave

This is needed because the application delete happens in a reverse
order. If everything is in sync-wave 0 (default) some of the used crd's
might be already removed, and makes the cr stuck.
Argocd would be also stuck on either ns, or projects (that are in the default
0 wave)

Author: darkdoc

values-hub.yaml

@@ -55,22 +55,31 @@ clusterGroup:
       project: hub
       chart: hashicorp-vault
       chartVersion: 0.1.*
+      annotations:
+        argocd.argoproj.io/sync-wave: "2"
     golang-external-secrets:
       name: golang-external-secrets
       namespace: golang-external-secrets
       project: hub
       chart: golang-external-secrets
       chartVersion: 0.1.*
+      annotations:
+        argocd.argoproj.io/sync-wave: "5"
     config-demo:
       name: config-demo
       namespace: config-demo
       project: config-demo
       path: charts/all/config-demo
+      annotations:
+        argocd.argoproj.io/sync-wave: "10"
+
     hello-world:
       name: hello-world
       namespace: hello-world
       project: hello-world
       path: charts/all/hello-world
+      annotations:
+        argocd.argoproj.io/sync-wave: "2"
   imperative:
     # NOTE: We *must* use lists and not hashes. As hashes lose ordering once parsed by helm
     # The default schedule is every 10 minutes: imperative.schedule