From 0b3d6e0c6c205a807219b06c3129d9e757f267af Mon Sep 17 00:00:00 2001 From: Owais Rehman Date: Fri, 15 Nov 2024 17:58:28 +0500 Subject: [PATCH 01/13] Updated numbering for bullet points --- .../add-build-environment/add-environment.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/content/for-developers/tutorials/outer-loop/add-build-environment/add-environment.md b/content/for-developers/tutorials/outer-loop/add-build-environment/add-environment.md index fc0d2894..75dfaa2e 100644 --- a/content/for-developers/tutorials/outer-loop/add-build-environment/add-environment.md +++ b/content/for-developers/tutorials/outer-loop/add-build-environment/add-environment.md @@ -10,7 +10,7 @@ Lets see how can we add an environment to an application in a tenant. Lets say, └── prod ``` -1. Add the Helm Chart of your application with production environment configurations. +2. Add the Helm Chart of your application with production environment configurations. ```bash └── gabbar @@ -21,7 +21,7 @@ Lets see how can we add an environment to an application in a tenant. Lets say, └── templates/ ``` -1. Add an folder `prod` inside `/argocd-apps`. Add an ArgoCD Application in this folder which points to `//prod`. +3. Add an folder `prod` inside `/argocd-apps`. Add an ArgoCD Application in this folder which points to `//prod`. ```yaml # Name: stakater-nordmart-review.yaml(APP_NAME.yaml) @@ -46,7 +46,7 @@ Lets see how can we add an environment to an application in a tenant. Lets say, selfHeal: true ``` -1. Add a folder called production (if not present) corresponding to the cluster name inside `argocd-apps` at root level, Add an ArgoCD Application in this folder which points to `/argocd-apps/prod`. +4. Add a folder called production (if not present) corresponding to the cluster name inside `argocd-apps` at root level, Add an ArgoCD Application in this folder which points to `/argocd-apps/prod`. ```yaml # Name: gabbar-prod.yaml (TENANT_NAME-ENV_NAME.yaml) @@ -71,7 +71,7 @@ Lets see how can we add an environment to an application in a tenant. Lets say, selfHeal: true ``` -1. You should have a similar folder structure at the end: +5. You should have a similar folder structure at the end: ```bash ├── gabbar @@ -88,4 +88,5 @@ Lets see how can we add an environment to an application in a tenant. Lets say, └── gabbar-prod.yaml ``` -1. Make sure Application that deploys applications inside `argocd-apps/cluster-name/` folder is deployed in relevant `infra-gitops-config` repository. +6. Make sure Application that deploys applications inside `argocd-apps/cluster-name/` folder is deployed in relevant `infra-gitops-config` repository. + From f5b486f4dbcabe7801ed6eeb4984243fddfc1dc5 Mon Sep 17 00:00:00 2001 From: Owais Rehman Date: Fri, 15 Nov 2024 18:59:41 +0500 Subject: [PATCH 02/13] Updated readme to be more generic and understanding --- .../add-build-environment/add-environment.md | 67 ++++++++++--------- 1 file changed, 35 insertions(+), 32 deletions(-) diff --git a/content/for-developers/tutorials/outer-loop/add-build-environment/add-environment.md b/content/for-developers/tutorials/outer-loop/add-build-environment/add-environment.md index 75dfaa2e..586d3196 100644 --- a/content/for-developers/tutorials/outer-loop/add-build-environment/add-environment.md +++ b/content/for-developers/tutorials/outer-loop/add-build-environment/add-environment.md @@ -2,43 +2,43 @@ Lets see how can we add an environment to an application in a tenant. Lets say, we have added a production cluster and want to add a new environment in application for it to be deployed on production. -1. Create a folder named `production` at `/` which corresponds to the production environment. Suppose `gabbar` as tenant name, `stakater-nordmart-review` as application name, `production` as cluster name, `prod` as environment name. +1. Create a folder named `` at `/` which corresponds to the production environment. Suppose `` as tenant name, `` as application name, `` as cluster name, `` as environment name. ```bash - └── gabbar - └── stakater-nordmart-review - └── prod + └── + └── + └── ``` 2. Add the Helm Chart of your application with production environment configurations. ```bash - └── gabbar - └── stakater-nordmart-review - └── prod + └── + └── + └── ├── Chart.yaml ├── values.yaml └── templates/ ``` -3. Add an folder `prod` inside `/argocd-apps`. Add an ArgoCD Application in this folder which points to `//prod`. +3. Add an folder `` inside `/argocd-apps`. Add an ArgoCD Application in this folder which points to `//`. ```yaml - # Name: stakater-nordmart-review.yaml(APP_NAME.yaml) - # Path: gabbar/argocd-apps/prod (TENANT_NAME/ argocd-apps/ENV_NAME/) + # Name: .yaml(APP_NAME.yaml) + # Path: /argocd-apps/ (TENANT_NAME/ argocd-apps/ENV_NAME/) apiVersion: argoproj.io/v1alpha1 kind: Application metadata: - name: gabbar-prod-stakater-nordmart-review - namespace: openshift-gitops + name: -- + namespace: rh-openshift-gitops-instance spec: destination: - namespace: TARGET_NAMESPACE + namespace: server: 'https://kubernetes.default.svc' - project: gabbar + project: source: - path: gabbar/stakater-nordmart-review/prod - repoURL: 'APPS_GITOPS_REPO_URL' + path: // + repoURL: targetRevision: HEAD syncPolicy: automated: @@ -46,24 +46,24 @@ Lets see how can we add an environment to an application in a tenant. Lets say, selfHeal: true ``` -4. Add a folder called production (if not present) corresponding to the cluster name inside `argocd-apps` at root level, Add an ArgoCD Application in this folder which points to `/argocd-apps/prod`. +4. Add a folder called production (if not present) corresponding to the cluster name inside `argocd-apps` at root level, Add an ArgoCD Application in this folder which points to `/argocd-apps/`. ```yaml - # Name: gabbar-prod.yaml (TENANT_NAME-ENV_NAME.yaml) - # Path: argocd-apps/prod + # Name: -.yaml (TENANT_NAME-ENV_NAME.yaml) + # Path: argocd-apps/ apiVersion: argoproj.io/v1alpha1 kind: Application metadata: - name: gabbar-prod - namespace: openshift-gitops + name: - + namespace: rh-openshift-gitops-instance spec: destination: - namespace: TARGET_NAMESPACE + namespace: server: 'https://kubernetes.default.svc' - project: gabbar + project: source: - path: gabbar/argocd-apps/prod - repoURL: 'APPS_GITOPS_REPO_URL' + path: /argocd-apps/ + repoURL: targetRevision: HEAD syncPolicy: automated: @@ -74,19 +74,22 @@ Lets see how can we add an environment to an application in a tenant. Lets say, 5. You should have a similar folder structure at the end: ```bash - ├── gabbar - | ├── stakater-nordmart-review - | | ├── prod + ├── + | ├── + | | ├── | | | ├── Chart.yaml | | | ├── values.yaml | | └── └── templates/ ├── └── argocd-apps - | └── prod - | └── stakater-nordmart-review.yaml + | └── + | └── .yaml └── argocd-apps - └── production (cluster name) - └── gabbar-prod.yaml + └── (cluster name) + └── -prod.yaml ``` 6. Make sure Application that deploys applications inside `argocd-apps/cluster-name/` folder is deployed in relevant `infra-gitops-config` repository. +!!! note + Anything defined in `` are values that needs to be replaced according to specific needs. + From 6665fbc7c2cec03399dac3308fa1555edeaf8b7c Mon Sep 17 00:00:00 2001 From: Owais Rehman Date: Fri, 15 Nov 2024 19:11:16 +0500 Subject: [PATCH 03/13] added extra space --- .../add-build-environment/add-environment.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/content/for-developers/tutorials/outer-loop/add-build-environment/add-environment.md b/content/for-developers/tutorials/outer-loop/add-build-environment/add-environment.md index 586d3196..2b0e40f5 100644 --- a/content/for-developers/tutorials/outer-loop/add-build-environment/add-environment.md +++ b/content/for-developers/tutorials/outer-loop/add-build-environment/add-environment.md @@ -4,11 +4,11 @@ Lets see how can we add an environment to an application in a tenant. Lets say, 1. Create a folder named `` at `/` which corresponds to the production environment. Suppose `` as tenant name, `` as application name, `` as cluster name, `` as environment name. - ```bash - └── - └── - └── - ``` + ```bash + └── + └── + └── + ``` 2. Add the Helm Chart of your application with production environment configurations. @@ -90,6 +90,6 @@ Lets see how can we add an environment to an application in a tenant. Lets say, 6. Make sure Application that deploys applications inside `argocd-apps/cluster-name/` folder is deployed in relevant `infra-gitops-config` repository. -!!! note - Anything defined in `` are values that needs to be replaced according to specific needs. +!!! note + Anything defined in `` are values that needs to be replaced according to specific needs. \ No newline at end of file From 2f0a3ef002aca56fea5ff9714f9eb0c91a9fe97e Mon Sep 17 00:00:00 2001 From: Owais Rehman Date: Fri, 15 Nov 2024 19:13:42 +0500 Subject: [PATCH 04/13] added whitespace --- .../outer-loop/add-build-environment/add-environment.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/for-developers/tutorials/outer-loop/add-build-environment/add-environment.md b/content/for-developers/tutorials/outer-loop/add-build-environment/add-environment.md index 2b0e40f5..5e132e9f 100644 --- a/content/for-developers/tutorials/outer-loop/add-build-environment/add-environment.md +++ b/content/for-developers/tutorials/outer-loop/add-build-environment/add-environment.md @@ -3,13 +3,13 @@ Lets see how can we add an environment to an application in a tenant. Lets say, we have added a production cluster and want to add a new environment in application for it to be deployed on production. 1. Create a folder named `` at `/` which corresponds to the production environment. Suppose `` as tenant name, `` as application name, `` as cluster name, `` as environment name. - + ```bash └── └── └── ``` - + 2. Add the Helm Chart of your application with production environment configurations. ```bash From 98e014131dc8ff84671dfdb418fa86073fba7bc5 Mon Sep 17 00:00:00 2001 From: Owais Rehman Date: Fri, 15 Nov 2024 19:15:31 +0500 Subject: [PATCH 05/13] removed extra whitespace --- .../outer-loop/add-build-environment/add-environment.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/for-developers/tutorials/outer-loop/add-build-environment/add-environment.md b/content/for-developers/tutorials/outer-loop/add-build-environment/add-environment.md index 5e132e9f..6c60170e 100644 --- a/content/for-developers/tutorials/outer-loop/add-build-environment/add-environment.md +++ b/content/for-developers/tutorials/outer-loop/add-build-environment/add-environment.md @@ -3,13 +3,13 @@ Lets see how can we add an environment to an application in a tenant. Lets say, we have added a production cluster and want to add a new environment in application for it to be deployed on production. 1. Create a folder named `` at `/` which corresponds to the production environment. Suppose `` as tenant name, `` as application name, `` as cluster name, `` as environment name. - + ```bash └── └── └── ``` - + 2. Add the Helm Chart of your application with production environment configurations. ```bash From 0d4b15561b998af7fe4158de88b156acbc676db4 Mon Sep 17 00:00:00 2001 From: Owais Rehman Date: Fri, 15 Nov 2024 19:17:42 +0500 Subject: [PATCH 06/13] minor experimental change --- .../outer-loop/add-build-environment/add-environment.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/for-developers/tutorials/outer-loop/add-build-environment/add-environment.md b/content/for-developers/tutorials/outer-loop/add-build-environment/add-environment.md index 6c60170e..e68cf6dd 100644 --- a/content/for-developers/tutorials/outer-loop/add-build-environment/add-environment.md +++ b/content/for-developers/tutorials/outer-loop/add-build-environment/add-environment.md @@ -10,7 +10,7 @@ Lets see how can we add an environment to an application in a tenant. Lets say, └── ``` -2. Add the Helm Chart of your application with production environment configurations. +1. Add the Helm Chart of your application with production environment configurations. ```bash └── From ee9869324c75cf2ce0e086b85cd0cf953f027d65 Mon Sep 17 00:00:00 2001 From: Owais Rehman Date: Fri, 15 Nov 2024 19:21:09 +0500 Subject: [PATCH 07/13] corrected list numbers and indentations --- .../add-build-environment/add-environment.md | 156 +++++++++--------- 1 file changed, 78 insertions(+), 78 deletions(-) diff --git a/content/for-developers/tutorials/outer-loop/add-build-environment/add-environment.md b/content/for-developers/tutorials/outer-loop/add-build-environment/add-environment.md index e68cf6dd..651b1da0 100644 --- a/content/for-developers/tutorials/outer-loop/add-build-environment/add-environment.md +++ b/content/for-developers/tutorials/outer-loop/add-build-environment/add-environment.md @@ -11,84 +11,84 @@ Lets see how can we add an environment to an application in a tenant. Lets say, ``` 1. Add the Helm Chart of your application with production environment configurations. - - ```bash - └── - └── - └── - ├── Chart.yaml - ├── values.yaml - └── templates/ - ``` - -3. Add an folder `` inside `/argocd-apps`. Add an ArgoCD Application in this folder which points to `//`. - - ```yaml - # Name: .yaml(APP_NAME.yaml) - # Path: /argocd-apps/ (TENANT_NAME/ argocd-apps/ENV_NAME/) - apiVersion: argoproj.io/v1alpha1 - kind: Application - metadata: - name: -- - namespace: rh-openshift-gitops-instance - spec: - destination: - namespace: - server: 'https://kubernetes.default.svc' - project: - source: - path: // - repoURL: - targetRevision: HEAD - syncPolicy: - automated: - prune: true - selfHeal: true - ``` - -4. Add a folder called production (if not present) corresponding to the cluster name inside `argocd-apps` at root level, Add an ArgoCD Application in this folder which points to `/argocd-apps/`. - - ```yaml - # Name: -.yaml (TENANT_NAME-ENV_NAME.yaml) - # Path: argocd-apps/ - apiVersion: argoproj.io/v1alpha1 - kind: Application - metadata: - name: - - namespace: rh-openshift-gitops-instance - spec: - destination: - namespace: - server: 'https://kubernetes.default.svc' - project: - source: - path: /argocd-apps/ - repoURL: - targetRevision: HEAD - syncPolicy: - automated: - prune: true - selfHeal: true - ``` - -5. You should have a similar folder structure at the end: - - ```bash - ├── - | ├── - | | ├── - | | | ├── Chart.yaml - | | | ├── values.yaml - | | └── └── templates/ - ├── └── argocd-apps - | └── - | └── .yaml - └── argocd-apps - └── (cluster name) - └── -prod.yaml - ``` - -6. Make sure Application that deploys applications inside `argocd-apps/cluster-name/` folder is deployed in relevant `infra-gitops-config` repository. + + ```bash + └── + └── + └── + ├── Chart.yaml + ├── values.yaml + └── templates/ + ``` + +1. Add an folder `` inside `/argocd-apps`. Add an ArgoCD Application in this folder which points to `//`. + + ```yaml + # Name: .yaml(APP_NAME.yaml) + # Path: /argocd-apps/ (TENANT_NAME/ argocd-apps/ENV_NAME/) + apiVersion: argoproj.io/v1alpha1 + kind: Application + metadata: + name: -- + namespace: rh-openshift-gitops-instance + spec: + destination: + namespace: + server: 'https://kubernetes.default.svc' + project: + source: + path: // + repoURL: + targetRevision: HEAD + syncPolicy: + automated: + prune: true + selfHeal: true + ``` + +1. Add a folder called production (if not present) corresponding to the cluster name inside `argocd-apps` at root level, Add an ArgoCD Application in this folder which points to `/argocd-apps/`. + + ```yaml + # Name: -.yaml (TENANT_NAME-ENV_NAME.yaml) + # Path: argocd-apps/ + apiVersion: argoproj.io/v1alpha1 + kind: Application + metadata: + name: - + namespace: rh-openshift-gitops-instance + spec: + destination: + namespace: + server: 'https://kubernetes.default.svc' + project: + source: + path: /argocd-apps/ + repoURL: + targetRevision: HEAD + syncPolicy: + automated: + prune: true + selfHeal: true + ``` + +1. You should have a similar folder structure at the end: + + ```bash + ├── + | ├── + | | ├── + | | | ├── Chart.yaml + | | | ├── values.yaml + | | └── └── templates/ + ├── └── argocd-apps + | └── + | └── .yaml + └── argocd-apps + └── (cluster name) + └── -prod.yaml + ``` + +1. Make sure Application that deploys applications inside `argocd-apps/cluster-name/` folder is deployed in relevant `infra-gitops-config` repository. !!! note From b1dab352bcdf88dca8669d346aa843e49f7ce12b Mon Sep 17 00:00:00 2001 From: Owais Rehman Date: Fri, 15 Nov 2024 19:24:20 +0500 Subject: [PATCH 08/13] nitpicks --- .../outer-loop/add-build-environment/add-environment.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/content/for-developers/tutorials/outer-loop/add-build-environment/add-environment.md b/content/for-developers/tutorials/outer-loop/add-build-environment/add-environment.md index 651b1da0..94f18c0b 100644 --- a/content/for-developers/tutorials/outer-loop/add-build-environment/add-environment.md +++ b/content/for-developers/tutorials/outer-loop/add-build-environment/add-environment.md @@ -90,6 +90,5 @@ Lets see how can we add an environment to an application in a tenant. Lets say, 1. Make sure Application that deploys applications inside `argocd-apps/cluster-name/` folder is deployed in relevant `infra-gitops-config` repository. - -!!! note - Anything defined in `` are values that needs to be replaced according to specific needs. \ No newline at end of file +!!! note + Anything defined in `` are values that needs to be replaced according to specific needs. From cf93747474779a1d26ddfbe4d423a99cbb63e148 Mon Sep 17 00:00:00 2001 From: Owais Rehman Date: Tue, 19 Nov 2024 13:38:32 +0500 Subject: [PATCH 09/13] Updated docs a bit --- .../add-build-environment/add-environment.md | 48 +++++++++++-------- 1 file changed, 28 insertions(+), 20 deletions(-) diff --git a/content/for-developers/tutorials/outer-loop/add-build-environment/add-environment.md b/content/for-developers/tutorials/outer-loop/add-build-environment/add-environment.md index 94f18c0b..3ba19c33 100644 --- a/content/for-developers/tutorials/outer-loop/add-build-environment/add-environment.md +++ b/content/for-developers/tutorials/outer-loop/add-build-environment/add-environment.md @@ -2,12 +2,12 @@ Lets see how can we add an environment to an application in a tenant. Lets say, we have added a production cluster and want to add a new environment in application for it to be deployed on production. -1. Create a folder named `` at `/` which corresponds to the production environment. Suppose `` as tenant name, `` as application name, `` as cluster name, `` as environment name. +1. Create a folder named `r-name>` at `/` which corresponds to the production environment. Suppose `` as tenant name, `` as application name, `` as cluster name, `` as environment name. ```bash └── └── - └── + └── ``` 1. Add the Helm Chart of your application with production environment configurations. @@ -15,30 +15,30 @@ Lets see how can we add an environment to an application in a tenant. Lets say, ```bash └── └── - └── + └── ├── Chart.yaml ├── values.yaml └── templates/ ``` -1. Add an folder `` inside `/argocd-apps`. Add an ArgoCD Application in this folder which points to `//`. +1. Add an folder `` inside `/argocd-apps`. Add an ArgoCD Application in this folder which points to `//`. ```yaml # Name: .yaml(APP_NAME.yaml) - # Path: /argocd-apps/ (TENANT_NAME/ argocd-apps/ENV_NAME/) + # Path: /argocd-apps/ (TENANT_NAME/ argocd-apps/ENV_NAME/) apiVersion: argoproj.io/v1alpha1 kind: Application metadata: - name: -- + name: -- namespace: rh-openshift-gitops-instance spec: destination: - namespace: + namespace: server: 'https://kubernetes.default.svc' project: source: - path: // - repoURL: + path: // + repoURL: targetRevision: HEAD syncPolicy: automated: @@ -46,24 +46,24 @@ Lets see how can we add an environment to an application in a tenant. Lets say, selfHeal: true ``` -1. Add a folder called production (if not present) corresponding to the cluster name inside `argocd-apps` at root level, Add an ArgoCD Application in this folder which points to `/argocd-apps/`. +1. Add a folder called production (if not present) corresponding to the cluster name inside `argocd-apps` at root level, Add an ArgoCD Application in this folder which points to `/argocd-apps/`. ```yaml - # Name: -.yaml (TENANT_NAME-ENV_NAME.yaml) - # Path: argocd-apps/ + # Name: -.yaml (TENANT_NAME-ENV_NAME.yaml) + # Path: argocd-apps/ apiVersion: argoproj.io/v1alpha1 kind: Application metadata: - name: - + name: - namespace: rh-openshift-gitops-instance spec: destination: - namespace: + namespace: server: 'https://kubernetes.default.svc' project: source: - path: /argocd-apps/ - repoURL: + path: /argocd-apps/ + repoURL: targetRevision: HEAD syncPolicy: automated: @@ -76,19 +76,27 @@ Lets see how can we add an environment to an application in a tenant. Lets say, ```bash ├── | ├── - | | ├── + | | ├── | | | ├── Chart.yaml | | | ├── values.yaml | | └── └── templates/ ├── └── argocd-apps - | └── + | └── | └── .yaml └── argocd-apps - └── (cluster name) + └── (cluster name) └── -prod.yaml ``` 1. Make sure Application that deploys applications inside `argocd-apps/cluster-name/` folder is deployed in relevant `infra-gitops-config` repository. !!! note - Anything defined in `` are values that needs to be replaced according to specific needs. + Anything defined in `` are values that needs to be replaced according to specific needs. + +Brief details about what each key means is defined below: +1. `tenant-name`: Name of the tenant where this environment needs to be deployed. +2. `app-name`: Name of the application where this environment will be used. +3. `cluster-name`: Name of the cluster. +4. `env-name`: Name of the environment. +5. `target-namespace`: Name of the namespace where this environment will be deployed. +6. `apps-gitops-repo-url`: URL for apps gitops repository. \ No newline at end of file From f6c46ec1716ad003b1a7030612408e940a8b1ff4 Mon Sep 17 00:00:00 2001 From: Owais Rehman Date: Tue, 19 Nov 2024 13:52:23 +0500 Subject: [PATCH 10/13] Nit picks --- .../add-build-environment/add-environment.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/content/for-developers/tutorials/outer-loop/add-build-environment/add-environment.md b/content/for-developers/tutorials/outer-loop/add-build-environment/add-environment.md index 3ba19c33..5126a385 100644 --- a/content/for-developers/tutorials/outer-loop/add-build-environment/add-environment.md +++ b/content/for-developers/tutorials/outer-loop/add-build-environment/add-environment.md @@ -2,7 +2,7 @@ Lets see how can we add an environment to an application in a tenant. Lets say, we have added a production cluster and want to add a new environment in application for it to be deployed on production. -1. Create a folder named `r-name>` at `/` which corresponds to the production environment. Suppose `` as tenant name, `` as application name, `` as cluster name, `` as environment name. +1. Create a folder named `` at `/` which corresponds to the production environment. Suppose `` as tenant name, `` as application name, `` as cluster name, `` as environment name. ```bash └── @@ -95,8 +95,8 @@ Lets see how can we add an environment to an application in a tenant. Lets say, Brief details about what each key means is defined below: 1. `tenant-name`: Name of the tenant where this environment needs to be deployed. -2. `app-name`: Name of the application where this environment will be used. -3. `cluster-name`: Name of the cluster. -4. `env-name`: Name of the environment. -5. `target-namespace`: Name of the namespace where this environment will be deployed. -6. `apps-gitops-repo-url`: URL for apps gitops repository. \ No newline at end of file +1. `app-name`: Name of the application where this environment will be used. +1. `cluster-name`: Name of the cluster. +1. `env-name`: Name of the environment. +1. `target-namespace`: Name of the namespace where this environment will be deployed. +1. `apps-gitops-repo-url`: URL for Apps Gitops repository. \ No newline at end of file From f9f855fe444fda88e23dff46fef6ed0b98616816 Mon Sep 17 00:00:00 2001 From: Owais Rehman Date: Tue, 19 Nov 2024 13:53:18 +0500 Subject: [PATCH 11/13] spell correct --- .../outer-loop/add-build-environment/add-environment.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/for-developers/tutorials/outer-loop/add-build-environment/add-environment.md b/content/for-developers/tutorials/outer-loop/add-build-environment/add-environment.md index 5126a385..17515337 100644 --- a/content/for-developers/tutorials/outer-loop/add-build-environment/add-environment.md +++ b/content/for-developers/tutorials/outer-loop/add-build-environment/add-environment.md @@ -99,4 +99,4 @@ Brief details about what each key means is defined below: 1. `cluster-name`: Name of the cluster. 1. `env-name`: Name of the environment. 1. `target-namespace`: Name of the namespace where this environment will be deployed. -1. `apps-gitops-repo-url`: URL for Apps Gitops repository. \ No newline at end of file +1. `apps-gitops-repo-url`: URL for Apps GitOps repository. \ No newline at end of file From 2168dcf33f6c32c614e0ab79328e906a808d092b Mon Sep 17 00:00:00 2001 From: Owais Rehman Date: Tue, 19 Nov 2024 13:55:23 +0500 Subject: [PATCH 12/13] markdown correction --- .../outer-loop/add-build-environment/add-environment.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/content/for-developers/tutorials/outer-loop/add-build-environment/add-environment.md b/content/for-developers/tutorials/outer-loop/add-build-environment/add-environment.md index 17515337..1ccf19f1 100644 --- a/content/for-developers/tutorials/outer-loop/add-build-environment/add-environment.md +++ b/content/for-developers/tutorials/outer-loop/add-build-environment/add-environment.md @@ -91,12 +91,13 @@ Lets see how can we add an environment to an application in a tenant. Lets say, 1. Make sure Application that deploys applications inside `argocd-apps/cluster-name/` folder is deployed in relevant `infra-gitops-config` repository. !!! note - Anything defined in `` are values that needs to be replaced according to specific needs. - + Anything defined in `` are values that needs to be replaced according to specific needs. + Brief details about what each key means is defined below: + 1. `tenant-name`: Name of the tenant where this environment needs to be deployed. 1. `app-name`: Name of the application where this environment will be used. -1. `cluster-name`: Name of the cluster. +1. `cluster-name`: Name of the cluster. 1. `env-name`: Name of the environment. 1. `target-namespace`: Name of the namespace where this environment will be deployed. -1. `apps-gitops-repo-url`: URL for Apps GitOps repository. \ No newline at end of file +1. `apps-gitops-repo-url`: URL for Apps GitOps repository. From 689d2c786f866fbd62d4d38bab8e39ded5dc85ac Mon Sep 17 00:00:00 2001 From: Owais Rehman Date: Tue, 19 Nov 2024 13:56:23 +0500 Subject: [PATCH 13/13] markdown nitpicks --- .../outer-loop/add-build-environment/add-environment.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/for-developers/tutorials/outer-loop/add-build-environment/add-environment.md b/content/for-developers/tutorials/outer-loop/add-build-environment/add-environment.md index 1ccf19f1..c55ff0b2 100644 --- a/content/for-developers/tutorials/outer-loop/add-build-environment/add-environment.md +++ b/content/for-developers/tutorials/outer-loop/add-build-environment/add-environment.md @@ -92,7 +92,7 @@ Lets see how can we add an environment to an application in a tenant. Lets say, !!! note Anything defined in `` are values that needs to be replaced according to specific needs. - + Brief details about what each key means is defined below: 1. `tenant-name`: Name of the tenant where this environment needs to be deployed.