customizing csync (#1)

csync/source-base/root-sync-git/setters.yaml

@@ -10,13 +10,13 @@ data:
   ### tier1: 'experimentation' or 'env'
 	### tier2: [client-name]
 	### tier34: [project-id] (we replace environment code with “x”)
-  id: id1
+  id: client-name
   ## Folder: 'csync' or 'tier1' or 'tier2'
   ## 'tier3' or 'tier4' are used only with RepoSync
-  folder: folder1
+  folder: tier2
 
   # Git repo values
   repo-url: https://AZDO-ORG@dev.azure.com/AZDO-ORG/AZDO-PROJECT/_git/REPO-NAME
   # repo-url: https://github.com/GITHUB-ORG/REPO-NAME # Alternate, GitHub
   repo-branch: main
-  repo-dir: deploy/env
+  repo-dir: tier2/deploy/env

csync/source-customization/dev/root-sync-git/setters-version.yaml

@@ -0,0 +1,9 @@
+apiVersion: v1
+kind: ConfigMap
+metadata:
+  name: setters-version
+  annotations:
+    config.kubernetes.io/local-config: 'true'
+data:
+  # set to HEAD or a git tag or a commit or a hash for the revision that should be checked out
+  version: HEAD

csync/source-customization/dev/root-sync-git/setters.yaml

@@ -0,0 +1,22 @@
+apiVersion: v1
+kind: ConfigMap
+metadata:
+  name: setters
+  annotations:
+    config.kubernetes.io/local-config: 'true'
+data:
+  # Used for naming of the root-sync
+  ## id :
+  ### tier1: 'experimentation' or 'env'
+	### tier2: [client-name]
+	### tier34: [project-id] (we replace environment code with “x”)
+  id: client-name
+  ## Folder: 'csync' or 'tier1' or 'tier2'
+  ## 'tier3' or 'tier4' are used only with RepoSync
+  folder: tier2
+
+  # Git repo values
+  repo-url: https://AZDO-ORG@dev.azure.com/AZDO-ORG/AZDO-PROJECT/_git/REPO-NAME
+  # repo-url: https://github.com/GITHUB-ORG/REPO-NAME # Alternate, GitHub
+  repo-branch: main
+  repo-dir: tier2/deploy/dev

csync/source-customization/preprod/root-sync-git/setters-version.yaml

@@ -0,0 +1,9 @@
+apiVersion: v1
+kind: ConfigMap
+metadata:
+  name: setters-version
+  annotations:
+    config.kubernetes.io/local-config: 'true'
+data:
+  # set to HEAD or a git tag or a commit or a hash for the revision that should be checked out
+  version: HEAD

csync/source-customization/preprod/root-sync-git/setters.yaml

@@ -0,0 +1,22 @@
+apiVersion: v1
+kind: ConfigMap
+metadata:
+  name: setters
+  annotations:
+    config.kubernetes.io/local-config: 'true'
+data:
+  # Used for naming of the root-sync
+  ## id :
+  ### tier1: 'experimentation' or 'env'
+	### tier2: [client-name]
+	### tier34: [project-id] (we replace environment code with “x”)
+  id: client-name
+  ## Folder: 'csync' or 'tier1' or 'tier2'
+  ## 'tier3' or 'tier4' are used only with RepoSync
+  folder: tier2
+
+  # Git repo values
+  repo-url: https://AZDO-ORG@dev.azure.com/AZDO-ORG/AZDO-PROJECT/_git/REPO-NAME
+  # repo-url: https://github.com/GITHUB-ORG/REPO-NAME # Alternate, GitHub
+  repo-branch: main
+  repo-dir: tier2/deploy/preprod

csync/source-customization/prod/root-sync-git/setters-version.yaml

@@ -0,0 +1,9 @@
+apiVersion: v1
+kind: ConfigMap
+metadata:
+  name: setters-version
+  annotations:
+    config.kubernetes.io/local-config: 'true'
+data:
+  # set to HEAD or a git tag or a commit or a hash for the revision that should be checked out
+  version: HEAD

csync/source-customization/prod/root-sync-git/setters.yaml

@@ -0,0 +1,22 @@
+apiVersion: v1
+kind: ConfigMap
+metadata:
+  name: setters
+  annotations:
+    config.kubernetes.io/local-config: 'true'
+data:
+  # Used for naming of the root-sync
+  ## id :
+  ### tier1: 'experimentation' or 'env'
+	### tier2: [client-name]
+	### tier34: [project-id] (we replace environment code with “x”)
+  id: client-name
+  ## Folder: 'csync' or 'tier1' or 'tier2'
+  ## 'tier3' or 'tier4' are used only with RepoSync
+  folder: tier2
+
+  # Git repo values
+  repo-url: https://AZDO-ORG@dev.azure.com/AZDO-ORG/AZDO-PROJECT/_git/REPO-NAME
+  # repo-url: https://github.com/GITHUB-ORG/REPO-NAME # Alternate, GitHub
+  repo-branch: main
+  repo-dir: tier2/deploy/prod