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/administration/user-self-management/manage-pats.md
+42-9Lines changed: 42 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ toc: true
8
8
##Git user token management
9
9
As a user in Codefresh, you must authorize access to your Git provider accounts and authenticate Git-based actions from Codefresh clients, per provisioned GitOps Runtime. This is done through the Git user token, which is an access token unique to each user. For more details, including required scopes and how the Git user token differs from the Git Runtime token, see[Git tokens in Codefresh]({{site.baseurl}}/docs/security/git-tokens/).
10
10
11
-
11
+
{% if page.collection != site.gitops_collection %}
12
12
The authorization mode depends on the authorization method set up by your account admin:
13
13
***OAuth2**
14
14
If your admin has set up authentication with OAuth2, you can authorize access using OAuth2.
@@ -27,18 +27,14 @@ If you have access to more than one GitOps Runtime in the same or in different a
27
27
For OAuth2, the administrator pre-configures the permissions and expiry date. Once you supply your credentials for authorization, you are automatically directed to the Git Personal Tokens page.
28
28
29
29
#####Before you begin
30
-
{% if page.collection != site.gitops_collection %}
31
30
Make sure you have:
32
31
* For Bitbucket only, your Bitbucket account username
33
32
* If needed, a_user access token_ from your Git provider with the required scopes:
* Make sure you have a_user access token_ with the required scopes for[GitHub](#generate-github-user-access-tokens)
41
-
{% endif %}
42
38
43
39
#####How to
44
40
1. In the Codefresh UI, on the toolbar, click your avatar, and then select**Git Personal Access Token**.
@@ -50,9 +46,7 @@ Make sure you have:
50
46
1. Complete the verification if required, as when two-factor authentication is configured, for example.
51
47
* For**Git user tokens**:
52
48
1. Expand**Advanced authorization options**.
53
-
{% if page.collection != site.gitops_collection %}
54
49
1. For Bitbucket, enter your**Bitbucket username**.
55
-
{% endif %}
56
50
1. In the**Personal Access Token** field, paste the token you generated.
57
51
58
52
{%
@@ -69,15 +63,54 @@ max-width="50%"
69
63
{:start="4"}
70
64
1. Click**Add Token**.
71
65
In the Git Personal Access Tokens list, you can see that the new token is assigned to the GitOps Runtime.
66
+
{% endif %}
67
+
68
+
69
+
{% if page.collection == site.gitops_collection %}
70
+
>**NOTE**
71
+
Codefresh GitOps does not officially support fine-grained tokens, or tokens with custom scopes. If you are using such tokens, make sure you turn off validation for Git tokens in the`values.yaml` file, as described in[Skipping token values.yaml]({{site.baseurl}}/docs/security/git-tokens#skipping-token-validation-in-valuesyaml).
72
+
73
+
##Authorize Git access to GitOps Runtimes
74
+
Authorize Git access to GitOps Runtimes through Git user access tokens from your Git provider.
75
+
76
+
If you have access to more than one GitOps Runtime in the same or in different accounts, you can use the same Git user token for all the Runtimes you have access to._You must however authorize access for each GitOps Runtime individually_.
77
+
78
+
79
+
#####Before you begin
80
+
81
+
* Make sure you have a_user access token_ with the required scopes for[GitHub](#generate-github-user-access-tokens)
82
+
83
+
#####How to
84
+
1. In the Codefresh UI, on the toolbar, click your avatar, and then select**Git Personal Access Token**.
85
+
1. Select the GitOps Runtime to authenticate to, and then click**Add Token**.
86
+
1. For**Git user tokens**:
87
+
1. Expand**Advanced authorization options**.
88
+
1. In the**Personal Access Token** field, paste the token you generated.
alt="Authorize access to GitOps Runtime with OAuth/Git user token"
97
+
caption="Authorize access to GitOps Runtime with OAuth/Git user token"
98
+
max-width="50%"
99
+
%}
100
+
101
+
{:start="4"}
102
+
1. Click**Add Token**.
103
+
In the Git Personal Access Tokens list, you can see that the new token is assigned to the GitOps Runtime.
104
+
{% endif %}
72
105
73
106
##Manage Git user tokens for GitOps Runtimes
74
-
Once you authorize access to one or more GitOps Runtimes through OAuth or Git user tokens, the GitOps Runtimes and their associated tokens are listed in the Git Personal Access Tokens page.
107
+
Once you authorize access to one or more GitOps Runtimes through{% if page.collection != site.gitops_collection %}OAuth or{% endif %} Git user tokens, the GitOps Runtimes and their associated tokens are listed in the Git Personal Access Tokens page.
75
108
76
109
#####Manage Git user access tokens
77
110
You can manage Git user tokens for any GitOps Runtime, without affecting the GitOps Runtime at the account-level. Deleting the Git user token for a GitOps Runtime will deny_you_ access to the Git repositories, Git Sources and other resources associated with that Runtime, while the Runtime itself is not affected.
78
111
79
112
#####Notifications for GitOps Runtimes
80
-
If you have turned on notifications for GitOps Runtimes, Codefresh alerts you toGitOps Runtimes with invalid or expired Git personal access tokens.
113
+
If you have turned on notifications for GitOps Runtimes, Codefresh alerts you tothose Runtimes with invalid or expired Git personal access tokens.
81
114
You can turn off these notifications for selectively for Runtimes for which these alerts are less critical.
Copy file name to clipboardExpand all lines: _docs/environments/manage-apps-in-environments.md
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -48,8 +48,10 @@ Promote a product or application from the Environments dashboard using one of tw
48
48
Drag a product or application with changes to the target environment to promote it. Customize the Promotion Settings to control promotion behavior for the environment.
49
49
This method is best for quick promotions to test changes within a specific environment, typically in internal environments.
Copy file name to clipboardExpand all lines: _docs/installation/gitops/git-sources.md
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,8 +10,10 @@ A Git Source is a unique entity created for use with GitOps Runtimes in Codefres
10
10
The Git Source connects to a Git repository within your organization, serving as an easy way to manage the deployment and configuration of Argo CD applications on clusters.
11
11
The Git repository referenced by the Git Source stores application manifests and other resources which are always synced to the cluster. Codefresh manages the Git Source itself as an Argo CD application.
12
12
13
-
Watch this video:
14
-
{::nomarkdown}{% if page.collection != site.gitops_collection %}<img src=../../../../images/icons/video-play-icon-blue.svg?display=inline-block>{% endif %}{% if page.collection == site.gitops_collection %}<img src=../../../images/icons/video-play-icon-blue.svg?display=inline-block>{% endif %}{:/}[Git Sources in Runtimes](https://www.youtube.com/watch?v=StKxdCcOIQc&t=2s){:target="\_blank"}
13
+
<iframewidth="560"height="315"src="https://www.youtube.com/embed/StKxdCcOIQc?si=s3tc2tcq7fwxBUbz"title="YouTube video player"frameborder="0"allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share"referrerpolicy="strict-origin-when-cross-origin"allowfullscreen></iframe>
14
+
15
+
<!--- Watch this video:
16
+
{::nomarkdown}{% if page.collection != site.gitops_collection %}<img src=../../../../images/icons/video-play-icon-blue.svg?display=inline-block>{% endif %}{% if page.collection == site.gitops_collection %}<img src=../../../images/icons/video-play-icon-blue.svg?display=inline-block>{% endif %}{:/} [Git Sources in Runtimes](https://www.youtube.com/watch?v=StKxdCcOIQc&t=2s){:target="\_blank"}-->
Copy file name to clipboardExpand all lines: _docs/installation/gitops/gitops-values-yaml-validation.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -79,9 +79,10 @@ global:
79
79
{% endhighlight %}
80
80
81
81
##Disable validation for custom/fine-grained Git tokens
82
-
When using token with custom scopes, or GitHub's fine-grained tokens (currently not officially supported by Codefresh),_skip token validation_ to avoid validation failures during installation.
82
+
When using token with custom scopes, or GitHub's fine-grained tokens (currently not officially supported by Codefresh),_for Runtime version v0.18.0 or lower, skip token validation_ to avoid validation failures during installation.
83
83
84
-
Add the`skipGitPermissionValidation` flag to your`values.yaml` file:
84
+
85
+
* Add the`skipGitPermissionValidation` flag to your`values.yaml` file:
85
86
86
87
```yaml
87
88
app-proxy:
@@ -105,6 +106,5 @@ where:
105
106
* `<version>` is the version of the runtime to install.
106
107
107
108
108
-
## Install first GitOps Runtime in account
109
-
If you are installing the first GitOps Runtime in your Codefresh account, follow the installation wizard for guided instructions.