Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commitbb959dc

Browse files
authored
Classic integration shared config name (#866)
* Add troubleshooting for naming conflictAdded note on unique names for integrations and added troubleshooting article* Update error-context-already-exists.mdUpdated troubleshooting article* Add note on unique name for intsAdded note on unique name requirement and xref to troubleshooting article* UpdatesAddede missing xref to troubleshooting* Update error-context-already-exists.md
1 parented23379 commitbb959dc

14 files changed

+80
-13
lines changed

‎_docs/integrations/amazon-web-services.md‎

Lines changed: 5 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,9 @@ Codefresh has native support for AWS in the following areas:
1515

1616
See also[other Amazon deployments](#other-amazon-deployments).
1717

18+
>**IMPORTANT**:
19+
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/).
20+
1821
##Amazon Container Registries
1922

2023
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}
2932
Codefresh has native support for connecting an EKS cluster through the integration options for Kubernetes in Pipeline Integrations.
3033
See[Adding an EKS cluster]({{site.baseurl}}/docs/integrations/kubernetes/#adding-eks-cluster) in[Kubernetes pipeline integrations]({{site.baseurl}}/docs/integrations/kubernetes/).
3134

32-
<!-- ask Kostis which is correct?
33-
{%
34-
include image.html
35-
lightbox="true"
36-
file="/images/integrations/aws/aws-integration.png"
37-
url="/images/integrations/aws/aws-integration.png"
38-
alt="Connecting an Amazon cluster"
39-
caption="Connecting a Amazon cluster"
40-
max-width="40%"
41-
%}
42-
-->
35+
4336
{%
4437
include image.html
4538
lightbox="true"
@@ -109,6 +102,7 @@ For any other Amazon deployment, you can use the [Amazon CLI from a Docker image
109102

110103

111104
##Related articles
105+
[Troubleshooting Error: context already exists]({{site.baseurl}}/docs/kb/articles/error-context-already-exists/)
112106
[Add your cluster]({{site.baseurl}}/docs/integrations/kubernetes/#connect-a-kubernetes-cluster)
113107
[Manage your Kubernetes cluster]({{site.baseurl}}/docs/deployments/kubernetes/manage-kubernetes/)
114108
[Cloning Git repositories]({{site.baseurl}}/docs/example-catalog/ci-examples/git-checkout/)

‎_docs/integrations/argocd.md‎

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ toc: true
66
---
77

88
>**IMPORTANT**:
9-
We are planning to deprecate the ArgoCD agent for Codefresh pipelines. It has now been replaced with the GitOpsruntime, that offers a superset of the functionality of the agent, and is also better integrated
9+
We are planning to deprecate the ArgoCD agent for Codefresh pipelines. It has now been replaced with the GitOpsRuntime, that offers a superset of the functionality of the agent, and is also better integrated
1010
with the Codefresh dashboards.
1111

1212
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
2626

2727
##Set up ArgoCD integration in Codefresh
2828

29+
>**IMPORTANT**:
30+
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.
31+
2932
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"}.
3033
1. Select**GitOps** and then click**Configure**.
3134
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
176179
will remain unaffected.
177180

178181
##Related articles
182+
[Troubleshooting Error: context already exists]({{site.baseurl}}/docs/kb/articles/error-context-already-exists/)
179183
[Environment Dashboard]({{site.baseurl}}/docs/deployments/kubernetes/environment-dashboard/)
180184
[Kubernetes integration]({{site.baseurl}}/docs/integrations/kubernetes/)
181185

‎_docs/integrations/cloud-storage.md‎

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,9 @@ For every cloud storage provider, you need to first create a storage bucket in y
1414

1515
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.
1616

17+
>**IMPORTANT**:
18+
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/).
19+
1720
1. In the Codefresh UI, on the toolbar, click the Settings icon, and then from the sidebar select**Pipeline Integrations**.
1821
1. Scroll down to**Cloud Storage**, and click**Configure**.
1922

‎_docs/integrations/codecov-integration.md‎

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -26,6 +26,9 @@ alt="Getting a Token from Codecov"
2626

2727
##Set up Codecov integration in Codefresh
2828

29+
>**IMPORTANT**:
30+
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/).
31+
2932

3033
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"}.
3134
1. Select**Codecov** and then click**Configure**.

‎_docs/integrations/docker-registries.md‎

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,12 +23,14 @@ Codefresh enables you to integrate with several Docker container registries, inc
2323
*[Quay.io](quay-io)
2424
*[GitHub Container Registry](github-container-registry)
2525

26-
For a different registry choose to configure using the[Other](other-registries) option.
26+
For a different registry, choose to configure using the[Other](other-registries) option.
2727

2828
The registries can either be public or private.
2929

3030
##General Configuration
3131

32+
>**IMPORTANT**:
33+
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/).
3234
3335
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"}.
3436
1. Select**Docker Registries** and then click**Configure**.

‎_docs/integrations/git-providers.md‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -42,6 +42,8 @@ By default, you have direct access to Git repositories that exist in the Git pro
4242
1. From the**Add Git Provider** drop-down, select the Git provider to add.
4343
1. Define the settings as required.
4444

45+
>**IMPORTANT**:
46+
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/).
4547
4648
{% include image.html lightbox="true" file="/images/integrations/codefresh-integrations.png" url="/images/integrations/codefresh-integrations.png" alt="Codefresh Account Integration" max-width="80%" %}
4749

‎_docs/integrations/google-cloud.md‎

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -21,6 +21,9 @@ Codefresh has native support for Google Cloud in the following areas:
2121

2222
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/).
2323

24+
>**IMPORTANT**:
25+
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/).
26+
2427
{%
2528
include image.html
2629
lightbox="true"

‎_docs/integrations/hashicorp-vault.md‎

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -28,6 +28,9 @@ Codefresh can use secrets from your HashiCorp Vault installation. This way you h
2828

2929
##Set up HashiCorp Vault integration in the Codefresh UI
3030

31+
>**IMPORTANT**:
32+
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/).
33+
3134
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"}.
3235
1. Select**Secret Store** and then click**Configure**.
3336
1. From the**Add Provider** dropdown, select**Hashicorp vault**.

‎_docs/integrations/helm.md‎

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -20,6 +20,9 @@ even if you don't have an external Helm repository. See our [quick start guide f
2020

2121
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).
2222

23+
>**IMPORTANT**:
24+
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/).
25+
2326
##Set up external Helm integration
2427

2528
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"}.

‎_docs/integrations/jira.md‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -26,6 +26,8 @@ When you add a new Jira integration in Codefresh, you can authenticate either us
2626
2727
*[Jira Account Details]({{site.baseurl}}/docs/integrations/notifications/jira-integration/#provide-account-details)
2828

29+
>**IMPORTANT**:
30+
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/).
2931
<br />
3032
3133
**Before you begin**

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp