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
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -436,9 +436,9 @@ You can reset the Shared Configuration Repo via the CLI when:
436
436
## Update Git credentials for GitOps Runtimes
437
437
438
438
Provisioned GitOps Runtimes require valid Git tokens at all times to authenticate Git actions by you as a user.
439
-
>These tokens are personal access tokens, specific to each user. As such,the usercan use the samepersonal access token for multipleruntimes.
439
+
TheseGittokens are personal access tokens, specific to each user. As such,youcan use the sameGit user token for multipleRuntimes.
440
440
441
-
>TIP:
441
+
>**TIP**:
442
442
Git credentials are synced to the Shared Configuration Repository defined during installation. If you change your Git credentials, the Git account must match that of the Shared repo. For example, if the Shared repo is defined as `http://github.com/my-org/isc.git` and the Git provider is defined as `bitbucket`, the update will fail.
443
443
444
444
**When to update**
@@ -453,13 +453,13 @@ Otherwise, you have to update Git tokens in the following situations:
453
453
**Update methods**
454
454
The methods for updating any Git token are the same regardless of the reason for the update:
455
455
* OAuth2 authorization, if your admin has registered an OAuth Application for Codefresh.
456
-
* Git access token authentication, by generating apersonal access token in your Git provider account with the correct scopes.
457
-
You can update yourpersonal access token in the UI or through the CLI.
456
+
* Git access token authentication, by generating aGit user token in your Git provider account with the correct scopes.
457
+
You can update yourGit user token in the UI or through the CLI.
458
458
459
459
### Update Git credentials in Codefresh UI
460
460
461
461
**Before you begin**
462
-
* To authenticate through a Gitaccess token, make sure your token is valid and has [the required scopes]({{site.baseurl}}/docs/reference/git-tokens/#git-personal-tokens)
462
+
* To authenticate through a Gituser token, make sure your token is valid and has [the required scopes]({{site.baseurl}}/docs/reference/git-tokens/#git-user-access-token-scopes)
463
463
464
464
**How to**
465
465
1. In the Codefresh UI, on the toolbar, click the **Settings** icon.
@@ -486,7 +486,7 @@ The methods for updating any Git token are the same regardless of the reason for
486
486
487
487
{:start="6"}
488
488
1. For OAuth2 authorization:
489
-
>NOTE:
489
+
>**NOTE**:
490
490
>If the application is not registered, you get an error. Contact your admin for help.
491
491
492
492
* Enter your credentials, and select **Sign In**.
@@ -506,8 +506,8 @@ The methods for updating any Git token are the same regardless of the reason for
506
506
1. For Git token authentication, paste the generated token in the **Git runtime token** field.
507
507
1. Click **Update Credentials**.
508
508
509
-
### Update Gitpersonal access token through CLI
510
-
If you are using Gitpersonal access tokens for authentication, you can also update them through the Codefresh CLI.
509
+
### Update Gituser token through CLI
510
+
If you are using Gituser tokens for authentication, you can also update them through the Codefresh CLI.