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
* Update hybrid runtime contentExposed bitbucket cloud and added note that outh2 does not support bitbucket cloud* Update runtime contentContent and x-ref updates* Update installation-options.md
`<ingressHost>` is the IP address or URL of the ingress host in the runtime cluster.
100
+
101
+
>OAuth2 is not supported for hybrid runtimes with Bitbucket Cloud as the Git provider. Users can authorize access with their[Git personal access tokens](({{site.baseurl}}/docs/administration/user-settings/#authorize-git-access-in-codefresh)) in such cases.
102
+
100
103
101
104
{:start="2"}
102
105
1. Note down the following, as you will need them to create the K8s secret for the Git OAuth2 application:
Copy file name to clipboardExpand all lines: _docs/runtime/installation-options.md
+7-4Lines changed: 7 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -50,13 +50,13 @@ Codefresh Runtime creates three repositories in your organization's Git provider
50
50
51
51
* Codefresh runtime installation repository
52
52
* Codefresh Git Sources
53
-
* Codefresh shared configuration repository. It does so for two types of entities:
53
+
* Codefresh shared configuration repository
54
54
55
-
**Codefresh Runtimefinctionality**
55
+
<!---**Codefresh Runtimefunctionality**
56
56
The runtime:
57
57
* Ensures that the installation repository and the Git Sources are always in sync, and applies Git changes back to the cluster
58
58
* Receives events and information from the user's organization systems to execute workflows
59
-
By default, the ingress controller directs all requests and events to the Codefresh Application Proxy. When internal and an external ingress hosts are configured, the ingress comtroller directs webhook events to the relevant Event Source and then to Argo Events (not via the Codefresh Application Proxy).
59
+
By default, the ingress controller directs all requests and events to the Codefresh Application Proxy. When internal and an external ingress hosts are configured, the ingress comtroller directs webhook events to the relevant Event Source and then to Argo Events (not via the Codefresh Application Proxy).-->
60
60
61
61
###Hosted vs.Hybrid environments
62
62
@@ -84,4 +84,7 @@ The table below highlights the main differences between hosted and hybrid enviro
Copy file name to clipboardExpand all lines: _docs/runtime/installation.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
@@ -54,7 +54,7 @@ For documentation purposes, the flags are grouped into:
54
54
Required.
55
55
The runtime name must start with a lower-case character, and can include up to 62 lower-case characters and numbers.
56
56
* CLI wizard: Add when prompted.
57
-
* Silent install:Required.
57
+
* Silent install:Specify the runtime name with the`--runtime` flag.
58
58
59
59
**Namespace resource labels**
60
60
Optional.
@@ -157,7 +157,7 @@ You can define any of the following Git providers:
157
157
*[GitLab Cloud](#gitlab-cloud)
158
158
*[GitLab Server](#gitlab-server)
159
159
* Bitbucket:
160
-
<!---* [Bitbucket Cloud](#bitbucket-cloud)-->
160
+
*[Bitbucket Cloud](#bitbucket-cloud)
161
161
*[Bitbucket Server](#bitbucket-server)
162
162
163
163
{::nomarkdown}
@@ -292,8 +292,8 @@ where:
292
292
</br>
293
293
{:/}
294
294
295
-
<!---##### Bitbucket Cloud
296
-
> For the required scopes, see [BitbucketCloud and Bitbucket Serverruntime token scopes]({{site.baseurl}}/docs/reference/git-tokens/#bitbucket-server-runtime-token-scopes).
295
+
#####Bitbucket Cloud
296
+
>For the required scopes, see[Bitbucket runtime token scopes]({{site.baseurl}}/docs/reference/git-tokens/#bitbucket-cloud-and-bitbucket-server-runtime-token-scopes).
*`--git-user <git_username>` (required), is your username for the Bitbucket Cloud account.
320
-
* `--git-token <git-runtime-token>` (required), is the Git token authenticating access to the runtime installation repository (see [Bitbucket runtime token scopes]{{site.baseurl}}/docs/reference/git-tokens/#bitbucket-server-runtime-token-scopes)).
320
+
*`--git-token <git-runtime-token>` (required), is the Git token authenticating access to the runtime installation repository (see[Bitbucket runtime token scopes]({{site.baseurl}}/docs/reference/git-tokens/#bitbucket-cloud-and-bitbucket-server-runtime-token-scopes)).
321
321
322
322
323
323
{::nomarkdown}
324
324
</br>
325
-
{:/}-->
325
+
{:/}
326
326
327
327
#####Bitbucket Server
328
328
329
-
>For the required scopes, see[BitbucketServerruntime token scopes]({{site.baseurl}}/docs/reference/git-tokens/#bitbucket-server-runtime-token-scopes).
329
+
>For the required scopes, see[Bitbucket runtime token scopes]({{site.baseurl}}/docs/reference/git-tokens/#bitbucket-cloud-and-bitbucket-server-runtime-token-scopes).
*`--git-user <git_username>` (required), is your username for the Bitbucket Server account.
353
-
*`--git-token <git-runtime-token>` (required), is the Git token authenticating access to the runtime installation repository (see[Bitbucket runtime token scopes]({{site.baseurl}}/docs/reference/git-tokens/#bitbucket-server-runtime-token-scopes)).
353
+
*`--git-token <git-runtime-token>` (required), is the Git token authenticating access to the runtime installation repository (see[Bitbucket runtime token scopes]({{site.baseurl}}/docs/reference/git-tokens/#bitbucket-cloud-and-bitbucket-server-runtime-token-scopes)).