Skip to content

Commit bab57fe

Browse files
Update creating.adoc
1 parent ce42c95 commit bab57fe

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

docs/modules/ROOT/pages/how-tos/creating.adoc

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
= Creating applications and components
22

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.
44

55
Once build pipelines are enabled, users can create their applications in {ProductName}. The second procedure below describes how to create an application.
66

@@ -13,7 +13,7 @@ Once build pipelines are enabled, users can create their applications in {Produc
1313

1414
.Procedure:
1515

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].
1717
. Start a new link:https://smee.io/[smee] channel.
1818
. 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.
1919

@@ -22,23 +22,23 @@ Once build pipelines are enabled, users can create their applications in {Produc
2222
.Prerequisites:
2323

2424
* link:https://kubernetes.io/docs/tasks/tools/[kubectl] CLI tool
25-
* The following values from your {ProductName} GitHub application:
25+
* The following values from your {ProductName} GitHub App:
2626
** The private key
27-
** The application ID
27+
** The App ID
2828
** The webhook secret
2929
* A GitHub repository with source code for your application
3030
** It must have the same basic structure as our example repository
3131
* Read/write access to the repository for your instance of {ProductName}
3232

3333
.Procedure:
3434

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.
3636
. 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:
3737
.. 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`.
3838
.. 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.
3939
+
4040
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.
4242
. Run the following command. Be sure to replace <namespace> with your actual namespace.
4343
+
4444
`kubectl create -f /test/resources/demo-users/user/<namespace>/application-and-component.yaml`

0 commit comments

Comments
 (0)