You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -151,6 +151,10 @@ The ArgoHub home page and all pages within the ArgoHub collection are excluded f
151
151
- Commandbar HelpHub Search (managed via Commandbar Content Manager).
152
152
- Search engines that support the`noindex` rule, such as Google.
153
153
154
+
####Commandbar's HelpHub and Copilot Content Sync
155
+
156
+
Commandbar synchronizes the documentation site content using a crawler. However, the Auto Redirect mechanism prevents the crawler from accessing all Enterprise pages (see the "Auto Redirect from Enterprise to ArgoHub Collection" section for details). To address this issue, the Commandbar team configured the crawler to include the`cfdoctype` cookie, enabling it to access all documentation pages and bypass the redirect.
157
+
154
158
###Auto Redirect from Enterprise to ArgoHub Collection
155
159
156
160
When the GitOps client adds an ArgoHub system type cookie, the Documentation site will detect it and initiate an automatic redirect. If you open any page from the enterprise collection, the site will check for an equivalent document in the ArgoHub collection and redirect you there if one exists.
Copy file name to clipboardExpand all lines: _docs/administration/account-user-management/service-accounts.md
-10Lines changed: 0 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -100,16 +100,6 @@ max-width="90%"
100
100
|**Status**| Indicates if the service account is currently active (**Enabled**) or inactive (**Disabled**). You may want to disable a service account to invalidate its API keys without having to remove the service account, and simply reenable when needed.|
101
101
|**Actions**| The options available to manage the service account through its context menu: {::nomarkdown}<ul><li><b>Edit</b>: Modify the settings of the service account, including adding/removing teams, enabling/disabling admin role.</li><li><b>Delete</b>: Delete the service account, including all the API keys defined for the account. This means that actions through the Codefresh API or CLI that require these keys will fail.</li></ul>{:/}|
102
102
103
-
{% if page.collection != site.gitops_collection %}
104
-
##Authenticating to Amazon ECR with service account
105
-
106
-
Authenticate to Amazon ECR registries with credentials from the service account instead of the Access Key ID and Secret Access Key.
107
-
This allows pipelines to seamlessly authenticate to Amazon ECR via service account credentials, enhancing security and simplifying access management.
108
-
109
-
There are two requirements:
110
-
1. Set the option to authenticate via service accounts at the account level for pipelines. See[Advanced options for pipelines]({{site.baseurl}}/docs/pipelines/configuration/pipeline-settings/#advanced-options-for-pipelines).
111
-
1. Configure Amazon ECR integration to use service account credentials. See[Amazon ECR Container Registry pipeline integration]({{site.baseurl}}/docs/integrations/docker-registries/amazon-ec2-container-registry/).
112
-
{% endif %}
113
103
114
104
##Related articles
115
105
{% if page.collection != site.gitops_collection %}
Copy file name to clipboardExpand all lines: _docs/deployments/gitops/application-configuration-settings.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -57,7 +57,7 @@ See [Application Groups]({{site.baseurl}}/docs/deployments/gitops/gitops-app-gro
57
57
58
58
###Source
59
59
The Git repository with the application resources.
60
-
{::nomarkdown}<ul> <li><b>Repository URL</b>: The URL of the Git repo or the Helm package repo with the application resources. <br>If SSH is configured for the runtime, you can connect to the repo with either HTTPS or SSH. On selecting the repository, Codefresh automatically updates the URL format. See <a href="https://codefresh.io/docs/docs/installation/gitops/manage-runtimes/#configure-ssh-for-gitops-runtimes">Configure SSH for runtimes</a>.<br>If the Argo CD project is not the <span style="font-family: var(--font-family-monospace); font-size: 87.5%; color: #ad6800; background-color: #fffbe6">default</span> project, make sure that the repo has the correct access roles for your application.<ul><li><b>Revision and Path</b>: Applies to Git repositories. </li><li><b>Chart</b>: Applies to Helm repositories. The name of the Helm package with all the resource definitions for the application, and the version. </li></ul>For more information, see <a href="https://argo-cd.readthedocs.io/en/stable/user-guide/tracking_strategies/" target="\_blank">Tracking and Deployment Strategies</a>.</li></ul>{:/}
60
+
{::nomarkdown}<ul> <li><b>Repository URL</b>: The URL of the Git repo or the Helm package repo with the application resources. <br>If SSH is configured for the Runtime, you can connect to the repo with SSH instead of HTTPS. On selecting the repository, Codefresh automatically updates the URL format. See <a href="https://codefresh.io/docs/docs/installation/gitops/manage-runtimes/#configure-ssh-for-gitops-runtimes">Configure SSH for runtimes</a>.<br>If the Argo CD project is not the <span style="font-family: var(--font-family-monospace); font-size: 87.5%; color: #ad6800; background-color: #fffbe6">default</span> project, make sure that the repo has the correct access roles for your application.<ul><li><b>Revision and Path</b>: Applies to Git repositories. </li><li><b>Chart and Version</b>: Applies to Helm repositories. The name of the Helm package with all the resource definitions for the application.<br>The version is the version of the chart itself in the chart’s <code class="highlighter-rouge">Chart.yaml</code> file.</li></ul>For more information, see <a href="https://argo-cd.readthedocs.io/en/stable/user-guide/tracking_strategies/" target="\_blank">Tracking and Deployment Strategies</a>.</li></ul>{:/}
Automate pre- and post-promotion actions during GitOps promotions in environments, ensuring quality, security, and compliance at each stage.
42
40
43
41
44
-
##Promoting applications
42
+
43
+
##Simple promotions for applications
45
44
46
45
Promote and deploy changes in applications across environments.
47
-
Start with simple manual promotion, then automatewith Promotion Flows—evolving fromsimplesequential promotions to advanced ones with environment dependencies.
46
+
Start with simple manual promotion across two environments, then automateacross multiple environments with asimplePromotion Flows.
Copy file name to clipboardExpand all lines: _docs/gitops-quick-start/multi-env-sequential-flow.md
+8-2Lines changed: 8 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -263,9 +263,15 @@ spec:
263
263
264
264
265
265
## What's next
266
-
The next quick start will guide you through adding Promotion Workflows to each environment in a Promotion Flow. Promotion Workflows act as gates for conditional promotions, giving you more control and flexibility over promotion processes.
266
+
Before we move to more advanced scenarios for promotion applications, we'll create another key entity which enhances the promotion process—Promotion Workflows.
267
+
Promotion Workflows are used in automated promotion flows to enforce quality, security, and compliance requirements at each stage of the promotion.