Commitb9581e7

authored

Gitops uninstall runtime command change (#1273)

* Update manage-runtimes.md* Updated terraform install section* Update git-tokens.md

1 parent9781ac3 commitb9581e7Copy full SHA for b9581e7

File tree

-7

lines changed

-7

lines changed

Lines changed: 2 additions & 2 deletions

Original file line number	Diff line number	Diff line change
`@@ -162,8 +162,8 @@ After completing the installation, you may need to perform additional configurat`
`162`	`162`
`163`	`163`	`You can also use Terraform to install an additional GitOps Runtime with the[Helm provider](https://registry.terraform.io/providers/hashicorp/helm/latest/docs){:target="\_blank"}.`
`164`	`164`
`165`		`-* The Shared Configuration Repository and Git provider are configured once per account and do not need to be set up again.`
`166`		-* EachRuntime must have a unique name within the account. If you used`codefresh` (the default) for the first Runtime, choose a different name to avoid installation failures.
	`165`	`+>NOTE`
	`166`	+EveryRuntimein an accountmust have a unique name. If you used`codefresh` (the default) for the first Runtime, choose a different name to avoid installation failures.
`167`	`167`
`168`	`168`
`169`	`169`	`Here is an example:`

Lines changed: 3 additions & 1 deletion

Original file line number	Diff line number	Diff line change
`@@ -555,7 +555,9 @@ Uninstalling a GitOps Runtime permanently removes:`
`555`	`555`
`556`	`556`	`{:start="6"}`
`557`	`557`	`1. Copy and run the uninstall command:`
`558`		-`RELEASE_NAME=$(helm ls -n codefresh-gitops-runtime -q) && helm uninstall ${RELEASE_NAME} -n codefresh-gitops-runtime`
	`558`	+`helm uninstall cf-gitops-runtime -n <runtime-namespace>`
	`559`	`+where:`
	`560`	+* `<runtime-namespace>` is the namespace where the Runtime is installed.
`559`	`561`
`560`	`562`	`{:start="7"}`
`561`	`563`	`1. Click Close to exit.`

Lines changed: 2 additions & 2 deletions

Original file line number	Diff line number	Diff line change
`@@ -165,8 +165,8 @@ After installation, go to GitOps Runtimes > List View:`
`165`	`165`
`166`	`166`	`You can also use Terraform to install additional GitOps Runtimes with the[Helm provider](https://registry.terraform.io/providers/hashicorp/helm/latest/docs){:target="\_blank"}.`
`167`	`167`
`168`		`-* The Shared Configuration Repository and Git provider are configured once per account and do not need to be set up again.`
`169`		-* EachRuntime must have a unique name within the account. If you used`codefresh` (the default) for the first Runtime, choose a different name to avoid installation failures.
	`168`	`+>NOTE`
	`169`	+EveryRuntimein an accountmust have a unique name. If you used`codefresh` (the default) for the first Runtime, choose a different name to avoid installation failures.
`170`	`170`
`171`	`171`
`172`	`172`	`Here is an example:`

Lines changed: 0 additions & 2 deletions

Original file line number	Diff line number	Diff line change
`@@ -18,8 +18,6 @@ Codefresh requires two types of Git tokens for authentication in GitOps, a Git R`
`18`	`18`	`>IMPORTANT`
`19`	`19`	`_Both tokens are always securely stored on your cluster_ and never locally on our platform.`
`20`	`20`
`21`		`-Users can also create and use Git tokens with custom scopes for both GitOps Runtimes and for Git repositories associated with the Runtimes that they need to access. See[Git user tokens with custom scopes](#git-user-tokens-with-custom-scopes).`
`22`		`-`
`23`	`21`	`##Git Runtime tokens versus Git user tokens in Codefresh`
`24`	`22`	`The table below summarizes the main differences between the Git Runtime token and Git user tokens in Codefresh.`
`25`	`23`

Comments

(0)