Apr 13, 2023 · Apr 4, 2023 · Apr 4, 2023 · Apr 4, 2023 · Apr 13, 2023 · Apr 13, 2023
diff --git a/_docs/gitops-integrations/container-registries.md b/_docs/gitops-integrations/container-registries.md
   max-width="50%"
   %}

 ### Related articles
 ## Related articles
 [CI GitOps integrations]({{site.baseurl}}/docs/gitops-integrations/ci-integrations/)
 [Issue-tracking GitOps integrations]({{site.baseurl}}/docs/gitops-integrations/issue-tracking/)
 [Shared configuration repo]({{site.baseurl}}/docs/reference/shared-configuration/)
diff --git a/_docs/gitops-integrations/container-registries/amazon-ecr.md b/_docs/gitops-integrations/container-registries/amazon-ecr.md
 toc: true
 ---

 Codefresh has native supportfor interacting with Amazon ECR (Elastic Container Registry),to push, pull, and deploy images.
 For information on adding an Amazon ECR integration for GitOps in Codefresh, see [Container registry GitOps integrations]({{site.baseurl}}/docs/gitops-integrations/container-registries/).
 Codefresh has native supportto interact with Amazon ECR (Elastic Container Registry),and push, pull, and deploy images.
 Forgeneralinformation on adding an Amazon ECR integration for GitOps in Codefresh, see [Container registry GitOps integrations]({{site.baseurl}}/docs/gitops-integrations/container-registries/).

 >Amazon ECR integration is supported only for Hybrid GitOps.

 ## GitOps Amazon ECR integration options

 You can set up the integration with Amazon ECR in one of two modes:
 * IAM (Identity and Access Management) role (dynamic integration)
  [IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles.html){:target="\_blank"} roles provide temporary security credentials for applications and services to access AWS resources securely, that expire after a period of time.
 * Access key and secret (static integration)
  Access keys consist of an access key ID and a secret access key, used to authenticate and authorize API requests to AWS services for a specific user.
  Unlike IAM roles, access keys are long-term credentials, without a default expiration date.

 >Amazon ECR integration with IAM Role is supported only for Hybrid GitOps.
  Access Key integration is supported for both Hosted and Hybrid GitOps.


 Both IAM and access key modes use AWS Identity and Access Management (IAM) to create the integration with Amazon ECR.
 For detailed information, see [How Amazon Elastic Container Registry Works with IAM](https://docs.aws.amazon.com/AmazonECR/latest/userguide/security_iam_service-with-iam.html){:target="\_blank"} and the [AWS security blog](https://aws.amazon.com/blogs/security/how-to-use-trust-policies-with-iam-roles/){:target="\_blank"}.

 ## Prerequisites


 ### IAM Role integration
 Before you configure settings in Codefresh to integrate Amazon ECR:
 * [Create an IAM (Identity and Access Management) role](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles.html){:target="\_blank"}

        "Condition": {}
 }
 ```
 For detailed information, see [How Amazon Elastic Container Registry Works with IAM](https://docs.aws.amazon.com/AmazonECR/latest/userguide/security_iam_service-with-iam.html){:target="\_blank"} and the [AWS security blog](https://aws.amazon.com/blogs/security/how-to-use-trust-policies-with-iam-roles/){:target="\_blank"}.


 ### Access Key integration
 You must generate an access key ID and the access secret for the IAM user, and download or copy them to a secure location.


 >The steps that follow describe access key generation through the AWS Management Console.
  We assume that you have created the IAM user for whom to generate the access key. See [Creating an IAM user in your AWS account](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_users_create.html){:target="\_blank"}.


 1. Sign in to the AWS **Management Console**, and go to the IAM dashboard.
 1. In the left pane, click **Users**, and select the IAM user for whom to generate an access key.
 1. Click the **Security credentials** tab.
 1. Below Access keys, click **Create access key**.
 1. From Access key best practices & alternatives, select **Command Line Interface (CLI)**.
 1. Select **I understand the above recommendation...** and then click **Next**.
 1. Enter an optional description and then click **Create access key**.
 1. Click **Download .csv file**, or copy the **Access key ID**, and the **Secret access key** which is automatically generated to a secure location.
  You will need to define them in the integration settings.
 1. Click **Done**.



 ## Amazon ECR-GitOps integration settings in Codefresh
 The table describes the arguments required for GitOps integrations with Amazon ECR in Codefresh.
 | Setting    | Description     |
 | ----------  |  -------- |
 | **Integration name**       | A friendly name for the integration. This is the name you will reference in the third-party CI platform/tool. |
 | **All Runtimes/Selected Runtimes**   | {::nomarkdown} The runtimes in the account with which to share the integration resource. <br>The integration resource is created in the Git repository with the shared configuration, within <span style="font-family: var(--font-family-monospace); font-size: 87.5%; color: #ad6800; background-color: #fffbe6">resources</span>. The exact location depends on whether the integration is shared with all or specific runtimes: <br><ul><li>All runtimes: Created in <span style="font-family: var(--font-family-monospace); font-size: 87.5%; color: #ad6800; background-color: #fffbe6">resources/all-runtimes-all-clusters/</span></li><li>Selected runtimes: Created in <span style="font-family: var(--font-family-monospace); font-size: 87.5%; color: #ad6800; background-color: #fffbe6">resources/runtimes/<runtime-name>/</span></li></ul> You can reference the Docker Hub integration in the CI tool. {:/}|
 | **IAM Role**       | The name of the IAM role you defined with the specific permissions for authentication to the ECR.|
 | **Region**       |The geographic region hosting thecontainer registry. Define the region nearest to you.|
 | **All Runtimes/Selected Runtimes**   | {::nomarkdown} The runtimes in the account with which to share the integration resource. <br>The integration resource is created in the Git repository with the shared configuration, within <code class="highlighter-rouge">resources</code>. The exact location depends on whether the integration is shared with all or specific runtimes: <br><ul><li>All runtimes: Created in <code class="highlighter-rouge">resources/all-runtimes-all-clusters/</code></li><li>Selected runtimes: Created in <code class="highlighter-rouge">resources/runtimes/<runtime-name></code></li></ul> You can reference the Docker Hub integration in the CI tool. {:/}|
 | **IAM Role settings**       |IAM Role integration is not supported for Hosted GitOps Runtimes.{::nomarkdown}<ul><li><b>IAM Role</b>:The name of the IAM role you defined with the specific permissions for authentication to the ECR registry.</li><li><b>Region</b>: The geographic region hosting the container registry. Define the region nearest to you.</li></ul>{:/}|
 | **Access Key settings**       |Access Key integration is supported for both Hosted and Hybrid GitOps Runtimes.{::nomarkdown}<ul><li><b>Access Key ID</b>:Theaccess key generated for the IAM user, and paired with the <b>Secret Access Key</b> for authentication to the ECR registry.</li><li><b>Secret Access Key</b>: The secret access key generated for and paired with the <b>Access Key</b> for authentication to the ECR registry.</li><li><b>Region</b>: Thegeographic region hosting theECR registry. Define the region nearest to you.</li></ul>{:/}|
 | **Test connection**       | Click to verify that you can connect to the specified instance before you commit changes. |


    {% include
   image.html
   lightbox="true"
   file="/images/integrations/aws/aws-int-settings.png"
   url="/images/integrations/aws/aws-int-settings.png"
   file="/images/integrations/aws/ecr-role-access-key-int-settings.png"
   url="/images/integrations/aws/ecr-role-access-key-int-settings.png"
   alt="Amazon ECR for image enrichment"
   caption="Amazon ECR for image enrichment"
   caption="Amazon ECRintegrationfor image enrichment"
   max-width="50%"
   %}

 For how-to instructions, see [Configure container registry integrations for GitOps in Codefresh]({{site.baseurl}}/docs/gitops-integrations/container-registries/#configure-container-registry-integrations-for-gitops-in-codefresh) and [Edit/delete container registry integrations for GitOps in Codefresh]({{site.baseurl}}/docs/gitops-integrations/container-registries/#editdelete-container-registry-integrations).
 For how-to instructions, see [Configure container registry integrations for GitOps in Codefresh]({{site.baseurl}}/docs/gitops-integrations/container-registries/#configure-container-registry-integrations-for-gitops-in-codefresh) and [Edit/delete container registry integrations for GitOps in Codefresh]({{site.baseurl}}/docs/gitops-integrations/container-registries/#editdelete-container-registry-integrations-for-gitops).


 ## Related articles
diff --git a/_docs/gitops-integrations/container-registries/dockerhub.md b/_docs/gitops-integrations/container-registries/dockerhub.md
 | Setting    | Description     |
 | ----------  |  -------- |
 | **Integration name**       | A friendly name for the integration. This is the name you will reference in the third-party CI platform/tool. |
 | **All Runtimes/Selected Runtimes**   | {::nomarkdown} The runtimes in the account with which to share the integration resource. <br>The integration resource is created in the Git repository with the shared configuration, within <span style="font-family: var(--font-family-monospace); font-size: 87.5%; color: #ad6800; background-color: #fffbe6">resources</span>. The exact location depends on whether the integration is shared with all or specific runtimes: <br><ul><li>All runtimes: Created in <span style="font-family: var(--font-family-monospace); font-size: 87.5%; color: #ad6800; background-color: #fffbe6">resources/all-runtimes-all-clusters/</span></li><li>Selected runtimes: Created in <span style="font-family: var(--font-family-monospace); font-size: 87.5%; color: #ad6800; background-color: #fffbe6">resources/runtimes/<runtime-name>/</span></li></ul> You can reference the Docker Hub integration in the CI tool. {:/}|
 | **All Runtimes/Selected Runtimes**   | {::nomarkdown} The runtimes in the account with which to share the integration resource. <br>The integration resource is created in the Git repository with the shared configuration, within <code class="highlighter-rouge">resources</code>. The exact location depends on whether the integration is shared with all or specific runtimes: <br><ul><li>All runtimes: Created in <code class="highlighter-rouge">resources/all-runtimes-all-clusters/</code></li><li>Selected runtimes: Created in <code class="highlighter-rouge">resources/runtimes/<runtime-name></code></li></ul> You can reference the Docker Hub integration in the CI tool. {:/}|
 | **Username**       | The Docker Hub username.|
 | **Password**       |  If you enabled two-factor authentication, enter the personal access token for your Docker Hub account for Codefresh to push images. Personal access tokens are more secure and can be revoked when needed. Codefresh can then push your images. If two-factor authentication is not enabled, enter the password of your Docker Hub account (not recommended).|
 | **Test connection**       | Click to verify that you can connect to the specified instance before you commit changes. |
   max-width="50%"
   %}

 For how-to instructions, see [Configure container registry integrations for GitOps in Codefresh]({{site.baseurl}}/docs/gitops-integrations/container-registries/#configure-container-registry-integrations-in-codefresh) and [Edit/delete container registry integrations for GitOps in Codefresh]({{site.baseurl}}/docs/gitops-integrations/container-registries/#editdelete-container-registry-integrations).
 For how-to instructions, see [Configure container registry integrations for GitOps in Codefresh]({{site.baseurl}}/docs/gitops-integrations/container-registries/#configure-container-registry-integrations-in-codefresh) and [Edit/delete container registry integrations for GitOps in Codefresh]({{site.baseurl}}/docs/gitops-integrations/container-registries/#editdelete-container-registry-integrations-for-gitops).

 ## Related articles
 [Shared configuration repo]({{site.baseurl}}/docs/reference/shared-configuration/)
diff --git a/_docs/gitops-integrations/container-registries/github-cr.md b/_docs/gitops-integrations/container-registries/github-cr.md
 | Setting    | Description  |
 | ----------  |  -------- |
 | **Integration name**       | A friendly name for the integration. This is the name you will reference in the third-party CI platform/tool. |
 | **All Runtimes/Selected Runtimes**   | {::nomarkdown} The runtimes in the account with which to share the integration resource. <br> The integration resource is created in the Git repository with the shared configuration, within <span style="font-family: var(--font-family-monospace); font-size: 87.5%; color: #ad6800; background-color: #fffbe6">resources</span>. The exact location depends on whether the integration is shared with all or specific runtimes: <br><ul><li>All runtimes: Created in <span style="font-family: var(--font-family-monospace); font-size: 87.5%; color: #ad6800; background-color: #fffbe6">resources/all-runtimes-all-clusters/</span></li><li>Selected runtimes: Created in <span style="font-family: var(--font-family-monospace); font-size: 87.5%; color: #ad6800; background-color: #fffbe6">resources/runtimes/<runtime-name>/</span></li></ul> {:/}|
 | **All Runtimes/Selected Runtimes**   | {::nomarkdown} The runtimes in the account with which to share the integration resource. <br> The integration resource is created in the Git repository with the shared configuration, within <code class="highlighter-rouge">resources</code>. The exact location depends on whether the integration is shared with all or specific runtimes: <br><ul><li>All runtimes: Created in <code class="highlighter-rouge">resources/all-runtimes-all-clusters/</code></li><li>Selected runtimes: Created in <code class="highlighter-rouge">resources/runtimes/<runtime-name></code></li></ul> {:/}|
 | **Domain**         | The GitHub registry domain and is set to `ghcr.io`.|
 | **Username**       | Your GitHub username.|
 | **GitHub Token**   | Your GitHub PAT (personal access token).|
   max-width="50%"
   %}

 For how-to instructions, see [Configure container registry integrations for GitOps in Codefresh]({{site.baseurl}}/docs/gitops-integrations/container-registries/#configure-container-registry-integrations-for-gitops-in-codefresh) and [Edit/delete container registry integrations for GitOps in Codefresh]({{site.baseurl}}/docs/gitops-integrations/container-registries/#editdelete-container-registry-integrations).
 For how-to instructions, see [Configure container registry integrations for GitOps in Codefresh]({{site.baseurl}}/docs/gitops-integrations/container-registries/#configure-container-registry-integrations-for-gitops-in-codefresh) and [Edit/delete container registry integrations for GitOps in Codefresh]({{site.baseurl}}/docs/gitops-integrations/container-registries/#editdelete-container-registry-integrations-for-gitops).

 ## Related articles
 [Shared configuration repo]({{site.baseurl}}/docs/reference/shared-configuration/)
diff --git a/_docs/gitops-integrations/container-registries/jfrog.md b/_docs/gitops-integrations/container-registries/jfrog.md
 | Setting    | Description  |
 | ----------  |  -------- |
 | **Integration name**       | A friendly name for the integration. This is the name you will reference in the third-party CI platform/tool. |
 | **All Runtimes/Selected Runtimes**   | {::nomarkdown} The runtimes in the account with which to share the integration resource. <br>The integration resource is created in the Git repository with the shared configuration, within <span style="font-family: var(--font-family-monospace); font-size: 87.5%; color: #ad6800; background-color: #fffbe6">resources</span>. The exact location depends on whether the integration is shared with all or specific runtimes: <br><ul><li>All runtimes: Created in <span style="font-family: var(--font-family-monospace); font-size: 87.5%; color: #ad6800; background-color: #fffbe6">resources/all-runtimes-all-clusters/</span></li><li>Selected runtimes: Created in <span style="font-family: var(--font-family-monospace); font-size: 87.5%; color: #ad6800; background-color: #fffbe6">resources/runtimes/<runtime-name>/</span></li></ul> {:/}|
 | **All Runtimes/Selected Runtimes**   | {::nomarkdown} The runtimes in the account with which to share the integration resource. <br>The integration resource is created in the Git repository with the shared configuration, within <code class="highlighter-rouge">resources</code>. The exact location depends on whether the integration is shared with all or specific runtimes: <br><ul><li>All runtimes: Created in <code class="highlighter-rouge">resources/all-runtimes-all-clusters/</code></li><li>Selected runtimes: Created in <code class="highlighter-rouge">resources/runtimes/<runtime-name></code></li></ul> {:/}|
 | **Server Name**    | The URL of the JFrog Artifactory server instance.|
 | **Username**       | The JFrog Artifactory username.|
 | **Password**       | The JFrog Artifactory password.|
   max-width="50%"
   %}

 For how-to instructions, see [Configure container registry integrations for GitOps in Codefresh]({{site.baseurl}}/docs/gitops-integrations/container-registries/#configure-container-registry-integrations-in-codefresh) and [Edit/delete container registry integrations for GitOps in Codefresh]({{site.baseurl}}/docs/gitops-integrations/container-registries/#editdelete-container-registry-integrations).
 For how-to instructions, see [Configure container registry integrations for GitOps in Codefresh]({{site.baseurl}}/docs/gitops-integrations/container-registries/#configure-container-registry-integrations-in-codefresh) and [Edit/delete container registry integrations for GitOps in Codefresh]({{site.baseurl}}/docs/gitops-integrations/container-registries/#editdelete-container-registry-integrations-for-gitops).


 ## Related articles
Original file line number	Diff line number	Diff line change
Expand Up		@@ -82,7 +82,7 @@ use it.
		max-width="50%"
		%}

		### Related articles
		## Related articles
		[CI GitOps integrations]({{site.baseurl}}/docs/gitops-integrations/ci-integrations/)
		[Issue-tracking GitOps integrations]({{site.baseurl}}/docs/gitops-integrations/issue-tracking/)
		[Shared configuration repo]({{site.baseurl}}/docs/reference/shared-configuration/)
Expand Down
Original file line number	Diff line number	Diff line change
Expand Up		@@ -6,12 +6,30 @@ sub_group: container-registries
		toc: true
		---

		Codefresh has native supportfor interacting with Amazon ECR (Elastic Container Registry),to push, pull, and deploy images.
		For information on adding an Amazon ECR integration for GitOps in Codefresh, see [Container registry GitOps integrations]({{site.baseurl}}/docs/gitops-integrations/container-registries/).
		Codefresh has native supportto interact with Amazon ECR (Elastic Container Registry),and push, pull, and deploy images.
		Forgeneralinformation on adding an Amazon ECR integration for GitOps in Codefresh, see [Container registry GitOps integrations]({{site.baseurl}}/docs/gitops-integrations/container-registries/).

		>Amazon ECR integration is supported only for Hybrid GitOps.

		## GitOps Amazon ECR integration options

		You can set up the integration with Amazon ECR in one of two modes:
		* IAM (Identity and Access Management) role (dynamic integration)
		[IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles.html){:target="\_blank"} roles provide temporary security credentials for applications and services to access AWS resources securely, that expire after a period of time.
		* Access key and secret (static integration)
		Access keys consist of an access key ID and a secret access key, used to authenticate and authorize API requests to AWS services for a specific user.
		Unlike IAM roles, access keys are long-term credentials, without a default expiration date.

		>Amazon ECR integration with IAM Role is supported only for Hybrid GitOps.
		Access Key integration is supported for both Hosted and Hybrid GitOps.


		Both IAM and access key modes use AWS Identity and Access Management (IAM) to create the integration with Amazon ECR.
		For detailed information, see [How Amazon Elastic Container Registry Works with IAM](https://docs.aws.amazon.com/AmazonECR/latest/userguide/security_iam_service-with-iam.html){:target="\_blank"} and the [AWS security blog](https://aws.amazon.com/blogs/security/how-to-use-trust-policies-with-iam-roles/){:target="\_blank"}.

		## Prerequisites


		### IAM Role integration
		Before you configure settings in Codefresh to integrate Amazon ECR:
		* [Create an IAM (Identity and Access Management) role](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles.html){:target="\_blank"}

Expand All		@@ -27,7 +45,28 @@ For example:
		"Condition": {}
		}
		```
		For detailed information, see [How Amazon Elastic Container Registry Works with IAM](https://docs.aws.amazon.com/AmazonECR/latest/userguide/security_iam_service-with-iam.html){:target="\_blank"} and the [AWS security blog](https://aws.amazon.com/blogs/security/how-to-use-trust-policies-with-iam-roles/){:target="\_blank"}.


		### Access Key integration
		You must generate an access key ID and the access secret for the IAM user, and download or copy them to a secure location.


		>The steps that follow describe access key generation through the AWS Management Console.
		We assume that you have created the IAM user for whom to generate the access key. See [Creating an IAM user in your AWS account](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_users_create.html){:target="\_blank"}.


		1. Sign in to the AWS Management Console, and go to the IAM dashboard.
		1. In the left pane, click Users, and select the IAM user for whom to generate an access key.
		1. Click the Security credentials tab.
		1. Below Access keys, click Create access key.
		1. From Access key best practices & alternatives, select Command Line Interface (CLI).
		1. Select I understand the above recommendation... and then click Next.
		1. Enter an optional description and then click Create access key.
		1. Click Download .csv file, or copy the Access key ID, and the Secret access key which is automatically generated to a secure location.
		You will need to define them in the integration settings.
		1. Click Done.



		## Amazon ECR-GitOps integration settings in Codefresh
		The table describes the arguments required for GitOps integrations with Amazon ECR in Codefresh.
Expand All		@@ -36,23 +75,23 @@ The table describes the arguments required for GitOps integrations with Amazon E
		\| Setting \| Description \|
		\| ---------- \| -------- \|
		\| Integration name \| A friendly name for the integration. This is the name you will reference in the third-party CI platform/tool. \|
		\| All Runtimes/Selected Runtimes \| {::nomarkdown} The runtimes in the account with which to share the integration resource. <br>The integration resource is created in the Git repository with the shared configuration, within <span style="font-family: var(--font-family-monospace); font-size: 87.5%; color: #ad6800; background-color: #fffbe6">resources</span>. The exact location depends on whether the integration is shared with all or specific runtimes: <br><ul><li>All runtimes: Created in <span style="font-family: var(--font-family-monospace); font-size: 87.5%; color: #ad6800; background-color: #fffbe6">resources/all-runtimes-all-clusters/</span></li><li>Selected runtimes: Created in <span style="font-family: var(--font-family-monospace); font-size: 87.5%; color: #ad6800; background-color: #fffbe6">resources/runtimes/<runtime-name>/</span></li></ul> You can reference the Docker Hub integration in the CI tool. {:/}\|
		\| IAM Role \| The name of the IAM role you defined with the specific permissions for authentication to the ECR.\|
		\| Region \|The geographic region hosting thecontainer registry. Define the region nearest to you.\|
		\| All Runtimes/Selected Runtimes \| {::nomarkdown} The runtimes in the account with which to share the integration resource. <br>The integration resource is created in the Git repository with the shared configuration, within <code class="highlighter-rouge">resources</code>. The exact location depends on whether the integration is shared with all or specific runtimes: <br><ul><li>All runtimes: Created in <code class="highlighter-rouge">resources/all-runtimes-all-clusters/</code></li><li>Selected runtimes: Created in <code class="highlighter-rouge">resources/runtimes/<runtime-name></code></li></ul> You can reference the Docker Hub integration in the CI tool. {:/}\|
		\| IAM Role settings \|IAM Role integration is not supported for Hosted GitOps Runtimes.{::nomarkdown}<ul><li><b>IAM Role</b>:The name of the IAM role you defined with the specific permissions for authentication to the ECR registry.</li><li><b>Region</b>: The geographic region hosting the container registry. Define the region nearest to you.</li></ul>{:/}\|
		\| Access Key settings \|Access Key integration is supported for both Hosted and Hybrid GitOps Runtimes.{::nomarkdown}<ul><li><b>Access Key ID</b>:Theaccess key generated for the IAM user, and paired with the <b>Secret Access Key</b> for authentication to the ECR registry.</li><li><b>Secret Access Key</b>: The secret access key generated for and paired with the <b>Access Key</b> for authentication to the ECR registry.</li><li><b>Region</b>: Thegeographic region hosting theECR registry. Define the region nearest to you.</li></ul>{:/}\|
		\| Test connection \| Click to verify that you can connect to the specified instance before you commit changes. \|


		{% include
		image.html
		lightbox="true"
		file="/images/integrations/aws/aws-int-settings.png"
		url="/images/integrations/aws/aws-int-settings.png"
		file="/images/integrations/aws/ecr-role-access-key-int-settings.png"
		url="/images/integrations/aws/ecr-role-access-key-int-settings.png"
		alt="Amazon ECR for image enrichment"
		caption="Amazon ECR for image enrichment"
		caption="Amazon ECRintegrationfor image enrichment"
		max-width="50%"
		%}

		For how-to instructions, see [Configure container registry integrations for GitOps in Codefresh]({{site.baseurl}}/docs/gitops-integrations/container-registries/#configure-container-registry-integrations-for-gitops-in-codefresh) and [Edit/delete container registry integrations for GitOps in Codefresh]({{site.baseurl}}/docs/gitops-integrations/container-registries/#editdelete-container-registry-integrations).
		For how-to instructions, see [Configure container registry integrations for GitOps in Codefresh]({{site.baseurl}}/docs/gitops-integrations/container-registries/#configure-container-registry-integrations-for-gitops-in-codefresh) and [Edit/delete container registry integrations for GitOps in Codefresh]({{site.baseurl}}/docs/gitops-integrations/container-registries/#editdelete-container-registry-integrations-for-gitops).


		## Related articles
Expand Down
Original file line number	Diff line number	Diff line change
Expand Up		@@ -23,7 +23,7 @@ The table describes the arguments required for Docker Hub GitOps integration in
		\| Setting \| Description \|
		\| ---------- \| -------- \|
		\| Integration name \| A friendly name for the integration. This is the name you will reference in the third-party CI platform/tool. \|
		\| All Runtimes/Selected Runtimes \| {::nomarkdown} The runtimes in the account with which to share the integration resource. <br>The integration resource is created in the Git repository with the shared configuration, within <span style="font-family: var(--font-family-monospace); font-size: 87.5%; color: #ad6800; background-color: #fffbe6">resources</span>. The exact location depends on whether the integration is shared with all or specific runtimes: <br><ul><li>All runtimes: Created in <span style="font-family: var(--font-family-monospace); font-size: 87.5%; color: #ad6800; background-color: #fffbe6">resources/all-runtimes-all-clusters/</span></li><li>Selected runtimes: Created in <span style="font-family: var(--font-family-monospace); font-size: 87.5%; color: #ad6800; background-color: #fffbe6">resources/runtimes/<runtime-name>/</span></li></ul> You can reference the Docker Hub integration in the CI tool. {:/}\|
		\| All Runtimes/Selected Runtimes \| {::nomarkdown} The runtimes in the account with which to share the integration resource. <br>The integration resource is created in the Git repository with the shared configuration, within <code class="highlighter-rouge">resources</code>. The exact location depends on whether the integration is shared with all or specific runtimes: <br><ul><li>All runtimes: Created in <code class="highlighter-rouge">resources/all-runtimes-all-clusters/</code></li><li>Selected runtimes: Created in <code class="highlighter-rouge">resources/runtimes/<runtime-name></code></li></ul> You can reference the Docker Hub integration in the CI tool. {:/}\|
		\| Username \| The Docker Hub username.\|
		\| Password \| If you enabled two-factor authentication, enter the personal access token for your Docker Hub account for Codefresh to push images. Personal access tokens are more secure and can be revoked when needed. Codefresh can then push your images. If two-factor authentication is not enabled, enter the password of your Docker Hub account (not recommended).\|
		\| Test connection \| Click to verify that you can connect to the specified instance before you commit changes. \|
Expand All		@@ -39,7 +39,7 @@ The table describes the arguments required for Docker Hub GitOps integration in
		max-width="50%"
		%}

		For how-to instructions, see [Configure container registry integrations for GitOps in Codefresh]({{site.baseurl}}/docs/gitops-integrations/container-registries/#configure-container-registry-integrations-in-codefresh) and [Edit/delete container registry integrations for GitOps in Codefresh]({{site.baseurl}}/docs/gitops-integrations/container-registries/#editdelete-container-registry-integrations).
		For how-to instructions, see [Configure container registry integrations for GitOps in Codefresh]({{site.baseurl}}/docs/gitops-integrations/container-registries/#configure-container-registry-integrations-in-codefresh) and [Edit/delete container registry integrations for GitOps in Codefresh]({{site.baseurl}}/docs/gitops-integrations/container-registries/#editdelete-container-registry-integrations-for-gitops).

		## Related articles
		[Shared configuration repo]({{site.baseurl}}/docs/reference/shared-configuration/)
Expand Down
Original file line number	Diff line number	Diff line change
Expand Up		@@ -27,7 +27,7 @@ Before you configure settings in Codefresh to integrate GitHub container registr
		\| Setting \| Description \|
		\| ---------- \| -------- \|
		\| Integration name \| A friendly name for the integration. This is the name you will reference in the third-party CI platform/tool. \|
		\| All Runtimes/Selected Runtimes \| {::nomarkdown} The runtimes in the account with which to share the integration resource. <br> The integration resource is created in the Git repository with the shared configuration, within <span style="font-family: var(--font-family-monospace); font-size: 87.5%; color: #ad6800; background-color: #fffbe6">resources</span>. The exact location depends on whether the integration is shared with all or specific runtimes: <br><ul><li>All runtimes: Created in <span style="font-family: var(--font-family-monospace); font-size: 87.5%; color: #ad6800; background-color: #fffbe6">resources/all-runtimes-all-clusters/</span></li><li>Selected runtimes: Created in <span style="font-family: var(--font-family-monospace); font-size: 87.5%; color: #ad6800; background-color: #fffbe6">resources/runtimes/<runtime-name>/</span></li></ul> {:/}\|
		\| All Runtimes/Selected Runtimes \| {::nomarkdown} The runtimes in the account with which to share the integration resource. <br> The integration resource is created in the Git repository with the shared configuration, within <code class="highlighter-rouge">resources</code>. The exact location depends on whether the integration is shared with all or specific runtimes: <br><ul><li>All runtimes: Created in <code class="highlighter-rouge">resources/all-runtimes-all-clusters/</code></li><li>Selected runtimes: Created in <code class="highlighter-rouge">resources/runtimes/<runtime-name></code></li></ul> {:/}\|
		\| Domain \| The GitHub registry domain and is set to `ghcr.io`.\|
		\| Username \| Your GitHub username.\|
		\| GitHub Token \| Your GitHub PAT (personal access token).\|
Expand All		@@ -44,7 +44,7 @@ Before you configure settings in Codefresh to integrate GitHub container registr
		max-width="50%"
		%}

		For how-to instructions, see [Configure container registry integrations for GitOps in Codefresh]({{site.baseurl}}/docs/gitops-integrations/container-registries/#configure-container-registry-integrations-for-gitops-in-codefresh) and [Edit/delete container registry integrations for GitOps in Codefresh]({{site.baseurl}}/docs/gitops-integrations/container-registries/#editdelete-container-registry-integrations).
		For how-to instructions, see [Configure container registry integrations for GitOps in Codefresh]({{site.baseurl}}/docs/gitops-integrations/container-registries/#configure-container-registry-integrations-for-gitops-in-codefresh) and [Edit/delete container registry integrations for GitOps in Codefresh]({{site.baseurl}}/docs/gitops-integrations/container-registries/#editdelete-container-registry-integrations-for-gitops).

		## Related articles
		[Shared configuration repo]({{site.baseurl}}/docs/reference/shared-configuration/)
Expand Down
Original file line number	Diff line number	Diff line change
Expand Up		@@ -17,7 +17,7 @@ For information on adding a JFrog Artifactory integration in Codefresh, see [Git
		\| Setting \| Description \|
		\| ---------- \| -------- \|
		\| Integration name \| A friendly name for the integration. This is the name you will reference in the third-party CI platform/tool. \|
		\| All Runtimes/Selected Runtimes \| {::nomarkdown} The runtimes in the account with which to share the integration resource. <br>The integration resource is created in the Git repository with the shared configuration, within <span style="font-family: var(--font-family-monospace); font-size: 87.5%; color: #ad6800; background-color: #fffbe6">resources</span>. The exact location depends on whether the integration is shared with all or specific runtimes: <br><ul><li>All runtimes: Created in <span style="font-family: var(--font-family-monospace); font-size: 87.5%; color: #ad6800; background-color: #fffbe6">resources/all-runtimes-all-clusters/</span></li><li>Selected runtimes: Created in <span style="font-family: var(--font-family-monospace); font-size: 87.5%; color: #ad6800; background-color: #fffbe6">resources/runtimes/<runtime-name>/</span></li></ul> {:/}\|
		\| All Runtimes/Selected Runtimes \| {::nomarkdown} The runtimes in the account with which to share the integration resource. <br>The integration resource is created in the Git repository with the shared configuration, within <code class="highlighter-rouge">resources</code>. The exact location depends on whether the integration is shared with all or specific runtimes: <br><ul><li>All runtimes: Created in <code class="highlighter-rouge">resources/all-runtimes-all-clusters/</code></li><li>Selected runtimes: Created in <code class="highlighter-rouge">resources/runtimes/<runtime-name></code></li></ul> {:/}\|
		\| Server Name \| The URL of the JFrog Artifactory server instance.\|
		\| Username \| The JFrog Artifactory username.\|
		\| Password \| The JFrog Artifactory password.\|
Expand All		@@ -34,7 +34,7 @@ For information on adding a JFrog Artifactory integration in Codefresh, see [Git
		max-width="50%"
		%}

		For how-to instructions, see [Configure container registry integrations for GitOps in Codefresh]({{site.baseurl}}/docs/gitops-integrations/container-registries/#configure-container-registry-integrations-in-codefresh) and [Edit/delete container registry integrations for GitOps in Codefresh]({{site.baseurl}}/docs/gitops-integrations/container-registries/#editdelete-container-registry-integrations).
		For how-to instructions, see [Configure container registry integrations for GitOps in Codefresh]({{site.baseurl}}/docs/gitops-integrations/container-registries/#configure-container-registry-integrations-in-codefresh) and [Edit/delete container registry integrations for GitOps in Codefresh]({{site.baseurl}}/docs/gitops-integrations/container-registries/#editdelete-container-registry-integrations-for-gitops).


		## Related articles
Expand Down