Skip to content

[enterprise-4.10] RHDEVDOCS-3619: Update the creating applications flow as per the latest UI changes #42672

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 2, 2022
Merged

[enterprise-4.10] RHDEVDOCS-3619: Update the creating applications flow as per the latest UI changes #42672

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 5 additions & 2 deletions modules/odc-importing-codebase-from-git-to-create-application.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,6 +28,7 @@ The following procedure walks you through the *From Git* option in the *Develope
. After the Git URL is validated, the recommended builder image is selected and marked with a star. If the builder image is not auto-detected, select a builder image. For the `https://github.com/sclorg/nodejs-ex` Git URL, by default the Node.js builder image is selected.
.. Optional: Use the *Builder Image Version* drop-down to specify a version.
.. Optional: Use the *Edit import strategy* to select a different strategy.
.. Optional: For the Node.js builder image, use the **Run command** field to override the command to run the application.

. In the *General* section:
.. In the *Application* field, enter a unique name for the application grouping, for example, `myapp`. Ensure that the application name is unique in a namespace.
Expand All @@ -51,7 +52,9 @@ The *Serverless Deployment* option is displayed in the *Import from git* form on

. In the *Pipelines* section, select *Add Pipeline*, and then click *Show Pipeline Visualization* to see the pipeline for the application.

. In the *Advanced Options* section, the *Create a route to the application* is selected by default so that you can access your application using a publicly available URL. You can clear the check box if you do not want to expose your application on a public route.
. Optional: In the *Advanced Options* section, the *Target port* and the *Create a route to the application* is selected by default so that you can access your application using a publicly available URL.
+
If your application does not expose its data on the default public port, 80, clear the check box, and set the target port number you want to expose.

. Optional: You can use the following advanced options to further customize your application:

Expand Down Expand Up @@ -82,4 +85,4 @@ Click the *Resource Limit* link to set the amount of *CPU* and *Memory* resource
Labels::
Click the *Labels* link to add custom labels to your application.

. Click *Create* to create the application and see its build status in the *Topology* view.
. Click *Create* to create the application and a success notification is displayed. You can see the build status of the application in the *Topology* view.