Classic integration shared config name (#866)

NimRegev · web-flow · commit bb959dc3c715 · 2023-12-11T16:24:35.000+02:00
* Add troubleshooting for naming conflict

Added note on unique names for integrations and added troubleshooting article

* Update error-context-already-exists.md

Updated troubleshooting article

* Add note on unique name for ints

Added note on unique name requirement and xref to troubleshooting article

* Updates

Addede missing xref to troubleshooting

* Update error-context-already-exists.md
diff --git a/_docs/integrations/amazon-web-services.md b/_docs/integrations/amazon-web-services.md
@@ -15,6 +15,9 @@ Codefresh has native support for AWS in the following areas:
 
 See also [other Amazon deployments](#other-amazon-deployments).
 
+>**IMPORTANT**:  
+The name assigned to the integration must be unique within the account. Using the same name for other integrations or Shared Configuration contexts within pipelines will result in conflicts.<br>For troubleshooting, see [Error: context already exists]({{site.baseurl}}/docs/kb/articles/error-context-already-exists/).
+
 ## Amazon Container Registries
 
 Amazon Container Registries are fully compliant with the Docker registry API that Codefresh follows. 
@@ -29,17 +32,7 @@ Once the registry is added, you can use the [standard push step]({{site.baseurl}
 Codefresh has native support for connecting an EKS cluster through the integration options for Kubernetes in Pipeline Integrations.
 See [Adding an EKS cluster]({{site.baseurl}}/docs/integrations/kubernetes/#adding-eks-cluster) in [Kubernetes pipeline integrations]({{site.baseurl}}/docs/integrations/kubernetes/).
 
-<!-- ask Kostis which is correct? 
-{% 
-	include image.html 
-	lightbox="true" 
-file="/images/integrations/aws/aws-integration.png" 
-url="/images/integrations/aws/aws-integration.png" 
-alt="Connecting an Amazon cluster" 
-caption="Connecting a Amazon cluster" 
-max-width="40%" 
-%}
--->
+
 {% 
 	include image.html 
 	lightbox="true" 
@@ -109,6 +102,7 @@ For any other Amazon deployment, you can use the [Amazon CLI from a Docker image
 
 
 ## Related articles
+[Troubleshooting Error: context already exists]({{site.baseurl}}/docs/kb/articles/error-context-already-exists/)  
 [Add your cluster]({{site.baseurl}}/docs/integrations/kubernetes/#connect-a-kubernetes-cluster)  
 [Manage your Kubernetes cluster]({{site.baseurl}}/docs/deployments/kubernetes/manage-kubernetes/)  
 [Cloning Git repositories]({{site.baseurl}}/docs/example-catalog/ci-examples/git-checkout/)  
diff --git a/_docs/integrations/argocd.md b/_docs/integrations/argocd.md
@@ -6,7 +6,7 @@ toc: true
 ---
 
 > **IMPORTANT**:  
-  We are planning to deprecate the ArgoCD agent for Codefresh pipelines. It has now been replaced with the GitOps runtime, that offers a superset of the functionality of the agent, and is also better integrated
+  We are planning to deprecate the ArgoCD agent for Codefresh pipelines. It has now been replaced with the GitOps Runtime, that offers a superset of the functionality of the agent, and is also better integrated
   with the Codefresh dashboards.  
 
   For an overview, read [Codefresh for GitOps]({{site.baseurl}}/docs/getting-started/gitops-codefresh/), and then click the links for detailed information.
@@ -26,6 +26,9 @@ Before you can use Codefresh and ArgoCD together, you need to connect your ArgoC
 
 ## Set up ArgoCD integration in Codefresh
 
+>**IMPORTANT**:  
+The name assigned to the integration must be unique within the account. Using the same name for other integrations or Shared Configuration contexts within pipelines will result in conflicts.
+
 1. In the Codefresh UI, on the toolbar, click the **Settings** icon, and then from the sidebar, select [**Pipeline Integrations**](https://g.codefresh.io/account-admin/account-conf/integration){:target="\_blank"}. 
 1. Select **GitOps** and then click **Configure**.
 1. From the **Add GitOps Provider** dropdown, select **ArgoCD**.
@@ -176,6 +179,7 @@ Note this will only uninstall the Codefresh agent. Your Argo CD installation
 will remain unaffected.
 
 ## Related articles
+[Troubleshooting Error: context already exists]({{site.baseurl}}/docs/kb/articles/error-context-already-exists/) 
 [Environment Dashboard]({{site.baseurl}}/docs/deployments/kubernetes/environment-dashboard/)  
 [Kubernetes integration]({{site.baseurl}}/docs/integrations/kubernetes/)  
 
diff --git a/_docs/integrations/cloud-storage.md b/_docs/integrations/cloud-storage.md
@@ -14,6 +14,9 @@ For every cloud storage provider, you need to first create a storage bucket in y
 
 When you connect your storage provider account to Codefresh, Codefresh creates subfolders in the storage bucket for every build, with the build IDs as folder names. Test reports generated for a build are uploaded to the respective folder. The same bucket can store test reports from multiple pipeline builds.
 
+>**IMPORTANT**:  
+The name assigned to the integration must be unique within the account. Using the same name for other integrations or Shared Configuration contexts within pipelines will result in conflicts. <br>For troubleshooting, see [Error: context already exists]({{site.baseurl}}/docs/kb/articles/error-context-already-exists/).
+
 1. In the Codefresh UI, on the toolbar, click the Settings icon, and then from the sidebar select **Pipeline Integrations**. 
 1. Scroll down to **Cloud Storage**, and click **Configure**.
 
diff --git a/_docs/integrations/codecov-integration.md b/_docs/integrations/codecov-integration.md
@@ -26,6 +26,9 @@ alt="Getting a Token from Codecov"
 
 ## Set up Codecov integration in Codefresh
 
+>**IMPORTANT**:  
+The name assigned to the integration must be unique within the account. Using the same name for other integrations or Shared Configuration contexts within pipelines will result in conflicts.<br>For troubleshooting, see [Error: context already exists]({{site.baseurl}}/docs/kb/articles/error-context-already-exists/).
+
 
 1. In the Codefresh UI, on the toolbar, click the **Settings** icon, and then from the sidebar, select [**Pipeline Integrations**](https://g.codefresh.io/account-admin/account-conf/integration){:target="\_blank"}. 
 1. Select **Codecov** and then click **Configure**.
diff --git a/_docs/integrations/docker-registries.md b/_docs/integrations/docker-registries.md
@@ -23,12 +23,14 @@ Codefresh enables you to integrate with several Docker container registries, inc
 * [Quay.io](quay-io)
 * [GitHub Container Registry](github-container-registry)
 
-For a different registry choose to configure using the [Other](other-registries) option.
+For a different registry, choose to configure using the [Other](other-registries) option.
 
 The registries can either be public or private.
 
 ## General Configuration
 
+>**IMPORTANT**:  
+The name assigned to the integration must be unique within the account. Using the same name for other integrations or Shared Configuration contexts within pipelines will result in conflicts.<br>For troubleshooting, see [Error: context already exists]({{site.baseurl}}/docs/kb/articles/error-context-already-exists/).
 
 1. In the Codefresh UI, on the toolbar, click the **Settings** icon, and then from the sidebar, select [**Pipeline Integrations**](https://g.codefresh.io/account-admin/account-conf/integration){:target="\_blank"}. 
 1. Select **Docker Registries** and then click **Configure**.
diff --git a/_docs/integrations/git-providers.md b/_docs/integrations/git-providers.md
@@ -42,6 +42,8 @@ By default, you have direct access to Git repositories that exist in the Git pro
 1. From the **Add Git Provider** drop-down, select the Git provider to add. 
 1. Define the settings as required. 
 
+>**IMPORTANT**:  
+The name assigned to the integration must be unique within the account. Using the same name for other integrations or Shared Configuration contexts within pipelines will result in conflicts.<br>For troubleshooting, see [Error: context already exists]({{site.baseurl}}/docs/kb/articles/error-context-already-exists/).
 
 {% include image.html lightbox="true" file="/images/integrations/codefresh-integrations.png" url="/images/integrations/codefresh-integrations.png" alt="Codefresh Account Integration" max-width="80%" %}
 
diff --git a/_docs/integrations/google-cloud.md b/_docs/integrations/google-cloud.md
@@ -21,6 +21,9 @@ Codefresh has native support for Google Cloud in the following areas:
 
 Google Container registries are fully compliant with the Docker registry API that Codefresh follows. You can connect GCR like any [other Docker registry]({{site.baseurl}}/docs/integrations/docker-registries/google-container-registry/).
 
+>**IMPORTANT**:  
+The name assigned to the integration must be unique within the account. Using the same name for other integrations or Shared Configuration contexts within pipelines will result in conflicts.<br>For troubleshooting, see [Error: context already exists]({{site.baseurl}}/docs/kb/articles/error-context-already-exists/).
+
 {% 
 	include image.html 
 	lightbox="true" 
diff --git a/_docs/integrations/hashicorp-vault.md b/_docs/integrations/hashicorp-vault.md
@@ -28,6 +28,9 @@ Codefresh can use secrets from your HashiCorp Vault installation. This way you h
 
 ## Set up HashiCorp Vault integration in the Codefresh UI
 
+>**IMPORTANT**:  
+The name assigned to the integration must be unique within the account. Using the same name for other integrations or Shared Configuration contexts within pipelines will result in conflicts.<br>For troubleshooting, see [Error: context already exists]({{site.baseurl}}/docs/kb/articles/error-context-already-exists/).
+
 1. In the Codefresh UI, on the toolbar, click the **Settings** icon, and then from the sidebar, select [**Pipeline Integrations**](https://g.codefresh.io/account-admin/account-conf/integration){:target="\_blank"}. 
 1. Select **Secret Store** and then click **Configure**.
 1. From the **Add Provider** dropdown, select **Hashicorp vault**.
diff --git a/_docs/integrations/helm.md b/_docs/integrations/helm.md
@@ -20,6 +20,9 @@ even if you don't have an external Helm repository. See our [quick start guide f
 
 For each Helm integration, you can toggle the level of access for [non-admin users]({{site.baseurl}}/docs/administration/account-user-management/access-control/#users-and-administrators). 
 
+>**IMPORTANT**:  
+The name assigned to the integration must be unique within the account. Using the same name for other integrations or Shared Configuration contexts within pipelines will result in conflicts.<br>For troubleshooting, see [Error: context already exists]({{site.baseurl}}/docs/kb/articles/error-context-already-exists/).
+
 ## Set up external Helm integration
 
 1. In the Codefresh UI, on the toolbar, click the **Settings** icon, and then from the sidebar, select [**Pipeline Integrations**](https://g.codefresh.io/account-admin/account-conf/integration){:target="\_blank"}. 
diff --git a/_docs/integrations/jira.md b/_docs/integrations/jira.md
@@ -26,6 +26,8 @@ When you add a new Jira integration in Codefresh, you can authenticate either us
  
 * [Jira Account Details]({{site.baseurl}}/docs/integrations/notifications/jira-integration/#provide-account-details)
 
+>**IMPORTANT**:  
+The name assigned to the integration must be unique within the account. Using the same name for other integrations or Shared Configuration contexts within pipelines will result in conflicts.<br>For troubleshooting, see [Error: context already exists]({{site.baseurl}}/docs/kb/articles/error-context-already-exists/).
 <br />
 
 **Before you begin**  
diff --git a/_docs/integrations/kubernetes.md b/_docs/integrations/kubernetes.md
@@ -27,6 +27,9 @@ Codefresh has native support for Kubernetes in the following areas:
 Codefresh offers its own Kubernetes dashboard that allows you to inspect the services and namespaces
 in your cluster. To activate this dashboard, you need to connect your cluster to your Codefresh account first.
 
+>**IMPORTANT**:  
+The name assigned to the integration must be unique within the account. Using the same name for other integrations or Shared Configuration contexts within pipelines will result in conflicts.<br>For troubleshooting, see [Error: context already exists]({{site.baseurl}}/docs/kb/articles/error-context-already-exists/).
+
 ## Connect a Kubernetes cluster
 
 ### Prerequisites
diff --git a/_docs/integrations/microsoft-azure.md b/_docs/integrations/microsoft-azure.md
@@ -17,6 +17,9 @@ Codefresh has native support for Azure in the following areas:
 - [Using Azure Storage for Helm charts]({{site.baseurl}}/docs/deployments/helm/helm-charts-and-repositories/)  
 - [Azure SSO]({{site.baseurl}}/docs/single-sign-on/oidc/oidc-azure/)
 
+>**IMPORTANT**:  
+The name assigned to the integration must be unique within the account. Using the same name for other integrations or Shared Configuration contexts within pipelines will result in conflicts.<br>For troubleshooting, see [Error: context already exists]({{site.baseurl}}/docs/kb/articles/error-context-already-exists/).
+
 ## Using Azure Git repositories
 
 Codefresh can easily check out code from Azure Git repositories:
diff --git a/_docs/integrations/secret-storage.md b/_docs/integrations/secret-storage.md
@@ -39,6 +39,10 @@ kubectl create configmap my-config-map --from-literal=key1=config1
 
 ### Set up Kubernetes secret integration in Codefresh UI
 
+
+>**IMPORTANT**:  
+The name assigned to the integration must be unique within the account. Using the same name for other integrations or Shared Configuration contexts within pipelines will result in conflicts.<br>For troubleshooting, see [Error: context already exists]({{site.baseurl}}/docs/kb/articles/error-context-already-exists/).
+
 1. In the Codefresh UI, on the toolbar, click the **Settings** icon, and then from the sidebar, select [**Pipeline Integrations**](https://g.codefresh.io/account-admin/account-conf/integration){:target="\_blank"}. 
 1. Select **Secret Store** and then click **Configure**.
 1. From the **Add Provider** dropdown, select **Kubernetes**.
diff --git a/_docs/kb/articles/error-context-already-exists.md b/_docs/kb/articles/error-context-already-exists.md
@@ -0,0 +1,38 @@
+---
+title: "Error: Context already exists"
+description: 
+group: kb
+sub-group: articles
+toc: true
+kb: true
+ht: false
+common: false
+categories: [Pipelines, Settings]
+support-reviewed: 2023-04-18 LG
+---
+
+Creating an integration or a Shared Configuration context for pipelines displays an error message that the `Context <context-name> already exists`.
+
+## Possible cause
+
+The name you provided for the integration or for the Shared Configuration context is already used by another integration/Shared Configuration context in your account.
+
+## Possible actions
+
+1. Get all contexts created for your account or contexts by type:  
+  `codefresh get contexts`  
+   
+_OR_ 
+
+  `codefresh get context --type <context-type>`
+
+   where:  
+   `<context-type>` is the type of context you want to retrieve, for example, `secret`
+
+{:start="2"}
+1. Change the name to make it unique in the account. 
+
+See [Get context](https://codefresh-io.github.io/cli/contexts/get-context/){:target="\_blank"} command description for all options.
+
+## Related articles
+[Shared configuration for pipelines]({{site.baseurl}}/docs/pipelines/configuration/shared-configuration/)  
