From c2b7a22f0fbcfa772f8a93c664a49a8c4238a95e Mon Sep 17 00:00:00 2001 From: NimRegev Date: Wed, 14 Dec 2022 12:01:45 +0200 Subject: [PATCH 1/5] Update monitor-manage-runtimes.md Added reset shared config repo procedure --- _docs/runtime/monitor-manage-runtimes.md | 20 ++++++++++++++++++-- 1 file changed, 18 insertions(+), 2 deletions(-) diff --git a/_docs/runtime/monitor-manage-runtimes.md b/_docs/runtime/monitor-manage-runtimes.md index 875b3703..b3418b78 100644 --- a/_docs/runtime/monitor-manage-runtimes.md +++ b/_docs/runtime/monitor-manage-runtimes.md @@ -27,8 +27,9 @@ Select the view mode to view runtime components and information, and manage prov Manage provisioned runtimes: -* [Add managed clusters to hybrid or hosted runtimes]({{site.baseurl}}/docs/runtime/managed-cluster/)) -* [Add and manage Git Sources associated with hybrid or hosted runtimes]({{site.baseurl}}/docs/runtime/git-sources/)) +* [Add managed clusters to hybrid or hosted runtimes]({{site.baseurl}}/docs/runtime/managed-cluster/) +* [Add and manage Git Sources associated with hybrid or hosted runtimes]({{site.baseurl}}/docs/runtime/git-sources/) +* [Reset shared configuration repository](#reset-shared-configuration-repository) * [Upgrade provisioned hybrid runtimes](#hybrid-upgrade-provisioned-runtimes) * [Upgrade Codefresh CLI](#upgrade-codefresh-cli) * [Uninstall provisioned runtimes](#uninstall-provisioned-runtimes) @@ -99,6 +100,21 @@ Here is a description of the information in the Topology view. |**Health/Sync status** |The health and sync status of the runtime or cluster. {::nomarkdown} {:/} | |**Search and View options** | {::nomarkdown} {:/}| +### Reset shared configuration repository +Reset the existing shared configuration repository for your account to allow Codefresh to initialize the shared configuration repo in the same account with a new runtime environment. + +Reset is useful when you want to use the same account for runtimes in a different environment. For example, if the shared configuration repo was used for POCs, and you now want to move to the production environment, or if you need to frequently switch between environments. In such cases, you can simply uninstall existing runtimes, and reset the shared repo. + +Codefresh creates the [shared configuration repository]({{site.baseule}}/docs/reference/shared-configuration) when you install first hybrid or hosted GitOps runtime for your account, and uses it for all runtimes you add to the same account. + +**Before you begin** +[Uninstall every runtime in the account](#uninstall-provisioned-runtimes) + +**How to** +* Run: + `cf config --reset-shared-config-repo` + + ### Upgrade Codefresh CLI The Codefresh CLI automatically self-checks its version, and if a newer version is available, prints a banner with the notification. From ae25c0f3eec3c9018f53aa29a80b7a92c238217e Mon Sep 17 00:00:00 2001 From: NimRegev Date: Wed, 14 Dec 2022 12:09:02 +0200 Subject: [PATCH 2/5] Update monitor-manage-runtimes.md --- _docs/runtime/monitor-manage-runtimes.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/_docs/runtime/monitor-manage-runtimes.md b/_docs/runtime/monitor-manage-runtimes.md index b3418b78..5dfa2bde 100644 --- a/_docs/runtime/monitor-manage-runtimes.md +++ b/_docs/runtime/monitor-manage-runtimes.md @@ -101,11 +101,15 @@ Here is a description of the information in the Topology view. |**Search and View options** | {::nomarkdown} {:/}| ### Reset shared configuration repository -Reset the existing shared configuration repository for your account to allow Codefresh to initialize the shared configuration repo in the same account with a new runtime environment. +Reset the location of the shared configuration repository for your account to initialize it for a new runtime environment. + +Reset is useful when you want to use the same account, but for runtimes in a different environment. For example, if the shared configuration repo was used for POCs, and you now want to move it to the production environment, or if you need to frequently switch between environments. In such cases, you can simply uninstall existing runtimes and reset the shared configuration repo. + +Codefresh creates the [shared configuration repository]({{site.baseurl}}/docs/reference/shared-configuration) when you install first hybrid or hosted GitOps runtime for your account, and uses it for all runtimes you add to the same account. + +>Reset shared configuration repo is supported from runtime v0.1.18 and higher. For runtimes with older versions, please contact Codefresh support. -Reset is useful when you want to use the same account for runtimes in a different environment. For example, if the shared configuration repo was used for POCs, and you now want to move to the production environment, or if you need to frequently switch between environments. In such cases, you can simply uninstall existing runtimes, and reset the shared repo. -Codefresh creates the [shared configuration repository]({{site.baseule}}/docs/reference/shared-configuration) when you install first hybrid or hosted GitOps runtime for your account, and uses it for all runtimes you add to the same account. **Before you begin** [Uninstall every runtime in the account](#uninstall-provisioned-runtimes) From 9c93017d35caacf211e5517c3560a9f1a4be0f52 Mon Sep 17 00:00:00 2001 From: NimRegev Date: Wed, 14 Dec 2022 13:48:37 +0200 Subject: [PATCH 3/5] Update monitor-manage-runtimes.md Updated with review comments --- _docs/runtime/monitor-manage-runtimes.md | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/_docs/runtime/monitor-manage-runtimes.md b/_docs/runtime/monitor-manage-runtimes.md index 5dfa2bde..a87ff460 100644 --- a/_docs/runtime/monitor-manage-runtimes.md +++ b/_docs/runtime/monitor-manage-runtimes.md @@ -101,14 +101,13 @@ Here is a description of the information in the Topology view. |**Search and View options** | {::nomarkdown}
  • Find a runtime or its clusters by typing part of the runtime/cluster name, and then navigate to the entries found.
  • Topology view options: Resize to window, zoom in, zoom out, full screen view.
{:/}| ### Reset shared configuration repository -Reset the location of the shared configuration repository for your account to initialize it for a new runtime environment. - -Reset is useful when you want to use the same account, but for runtimes in a different environment. For example, if the shared configuration repo was used for POCs, and you now want to move it to the production environment, or if you need to frequently switch between environments. In such cases, you can simply uninstall existing runtimes and reset the shared configuration repo. - Codefresh creates the [shared configuration repository]({{site.baseurl}}/docs/reference/shared-configuration) when you install first hybrid or hosted GitOps runtime for your account, and uses it for all runtimes you add to the same account. ->Reset shared configuration repo is supported from runtime v0.1.18 and higher. For runtimes with older versions, please contact Codefresh support. +If needed, you can reset the location of the shared configuration repository in your account to re-initialize it for a different runtime environment. For example, when moving from evaluation to production. +Uninstall all the existing runtimes in your account, and then run the reset command. On the next installation, Codefresh re-initializes the shared configuration repo. + +>Reset shared configuration repo is supported from CLI v0.1.18 and higher. **Before you begin** From 37cc571fcbd7f318894110db902650eba5d54a95 Mon Sep 17 00:00:00 2001 From: NimRegev Date: Wed, 14 Dec 2022 15:41:32 +0200 Subject: [PATCH 4/5] Update monitor-manage-runtimes.md Final content changes --- _docs/runtime/monitor-manage-runtimes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_docs/runtime/monitor-manage-runtimes.md b/_docs/runtime/monitor-manage-runtimes.md index a87ff460..0c08cb44 100644 --- a/_docs/runtime/monitor-manage-runtimes.md +++ b/_docs/runtime/monitor-manage-runtimes.md @@ -103,7 +103,7 @@ Here is a description of the information in the Topology view. ### Reset shared configuration repository Codefresh creates the [shared configuration repository]({{site.baseurl}}/docs/reference/shared-configuration) when you install first hybrid or hosted GitOps runtime for your account, and uses it for all runtimes you add to the same account. -If needed, you can reset the location of the shared configuration repository in your account to re-initialize it for a different runtime environment. For example, when moving from evaluation to production. +If needed, you can reset the location of the shared configuration repository in your account and re-initialize it. For example, when moving from evaluation to production. Uninstall all the existing runtimes in your account, and then run the reset command. On the next installation, Codefresh re-initializes the shared configuration repo. From eca4a9f493c2c28a627d86a4a90fe2e31efd1f4a Mon Sep 17 00:00:00 2001 From: NimRegev Date: Wed, 14 Dec 2022 15:48:18 +0200 Subject: [PATCH 5/5] Update monitor-manage-runtimes.md --- _docs/runtime/monitor-manage-runtimes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_docs/runtime/monitor-manage-runtimes.md b/_docs/runtime/monitor-manage-runtimes.md index 0c08cb44..d985199c 100644 --- a/_docs/runtime/monitor-manage-runtimes.md +++ b/_docs/runtime/monitor-manage-runtimes.md @@ -101,7 +101,7 @@ Here is a description of the information in the Topology view. |**Search and View options** | {::nomarkdown}
  • Find a runtime or its clusters by typing part of the runtime/cluster name, and then navigate to the entries found.
  • Topology view options: Resize to window, zoom in, zoom out, full screen view.
{:/}| ### Reset shared configuration repository -Codefresh creates the [shared configuration repository]({{site.baseurl}}/docs/reference/shared-configuration) when you install first hybrid or hosted GitOps runtime for your account, and uses it for all runtimes you add to the same account. +Codefresh creates the [shared configuration repository]({{site.baseurl}}/docs/reference/shared-configuration) when you install the first hybrid or hosted GitOps runtime for your account, and uses it for all runtimes you add to the same account. If needed, you can reset the location of the shared configuration repository in your account and re-initialize it. For example, when moving from evaluation to production. Uninstall all the existing runtimes in your account, and then run the reset command. On the next installation, Codefresh re-initializes the shared configuration repo.