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/modules/ROOT/pages/how-tos/creating.adoc
+6-6Lines changed: 6 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
= Creating applications and components
2
2
3
-
To create an application in {ProductName}, someone must enable build pipelines in your instance of {ProductName}. This includes creating a GitHub application, so {ProductName} can access users' pull requests, and configuring a smee channel, to listen for those PRs. The first procedure in this document explains how to perform these tasks.
3
+
To create an application in {ProductName}, someone must enable build pipelines in your instance of {ProductName}. This includes creating a GitHub App, so {ProductName} can access users' pull requests, and configuring a smee channel, to listen for those PRs. The first procedure in this document explains how to perform these tasks.
4
4
5
5
Once build pipelines are enabled, users can create their applications in {ProductName}. The second procedure below describes how to create an application.
6
6
@@ -13,7 +13,7 @@ Once build pipelines are enabled, users can create their applications in {Produc
13
13
14
14
.Procedure:
15
15
16
-
. Create a GitHub app according to link:https://pipelinesascode.com/docs/install/github_apps/#manual-setup[these Pipelines as Code instructions].
16
+
. Create a GitHub App according to link:https://pipelinesascode.com/docs/install/github_apps/#manual-setup[these Pipelines as Code instructions].
17
17
. Start a new link:https://smee.io/[smee] channel.
18
18
. In the repository for your instance of {ProductName}, edit the file /smee/smee-client.yaml. Replace <smee-channel> with the webhook proxy URL from the previous step.
19
19
@@ -22,23 +22,23 @@ Once build pipelines are enabled, users can create their applications in {Produc
* The following values from your {ProductName} GitHub application:
25
+
* The following values from your {ProductName} GitHub App:
26
26
** The private key
27
-
** The application ID
27
+
** The App ID
28
28
** The webhook secret
29
29
* A GitHub repository with source code for your application
30
30
** It must have the same basic structure as our example repository
31
31
* Read/write access to the repository for your instance of {ProductName}
32
32
33
33
.Procedure:
34
34
35
-
. In the GitHub repository for your application, install your organization’s {ProductName} GitHub application.
35
+
. In the GitHub repository for your application, install your organization’s {ProductName} GitHub App.
36
36
. In the repository for your instance of {ProductName}, you need to replace two `url` values in the relevant YAML file for your namespace. The path for this file is `/test/resources/demo-users/user/<namespace>/application-and-component.yaml`. Replace the two `url` values as follows:
37
37
.. For the `url` value beneath `git`, provide the URL that you would use to locally clone your application’s repository. This URL ends with `.git`.
38
38
.. For the `url` value beneath `spec`, at the end of the file, provide the URL for your application’s repository that you see in your browser, without `.git` at the end.
39
39
+
40
40
NOTE: To add other components to the same namespace, reference the example YAML file beneath this procedure.
41
-
. Login to {ProductName} xref:../getting-started/cli.adoc[through your CLI].
41
+
. Login to the Kubernetes cluster where Konflux is deployed.
42
42
. Run the following command. Be sure to replace <namespace> with your actual namespace.
0 commit comments