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: _docs/installation/gitops/monitor-manage-runtimes.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -256,7 +256,7 @@ If you have managed clusters for Hybrid GitOps Runtimes, upgrading the Runtime a
256
256
%}
257
257
258
258
{:start="5"}
259
-
1. Do one of the following depending on whether you have configured the Runtime asa Argo CD Application or not:
259
+
1. Do one of the following depending on whether you have configured the Runtime asan Argo CD Application or not:
260
260
* Argo CDGitOps Runtimes:Continue from step _6_.
261
261
* Non-Argo CD GitOps Runtimes: Continue from step _7_.
262
262
1. For GitOps Runtimes, do the following:
@@ -514,7 +514,7 @@ If you are using Git personal access tokens for authentication, you can also upd
514
514
515
515
where:
516
516
* `<repo_url>` is required, and is the URL of the Shared Configuration Repository, and must match the Git provider.
517
-
* `--git-provider` is optional for cloud providers as Codefresh identifiesthemthrough the Shared repo URL, and is requiredfor on-premises providers.
517
+
* `--git-provider` is optional for cloud providers as Codefresh identifiesthe providerthrough the Shared repo URL. Requiredfor on-premises providers, and can be one of the following: