Skip to content

Commit e92ac90

Browse files
committed
Fix pre-commit
1 parent 2d6ebc9 commit e92ac90

File tree

1 file changed

+13
-3
lines changed

1 file changed

+13
-3
lines changed

docs/OCP_CI_Tutorials/Triggering/Triggering_Guide.md

+13-3
Original file line numberDiff line numberDiff line change
@@ -135,6 +135,7 @@ In practice, the application currently served in the Openshift-Ci env is configu
135135
Since the tool is based on the Flask framework, it is natural to deploy a Lightsail container and the configuration is quite easy, with respect to the tool's current configuration options.
136136

137137
Step by step deployment:
138+
138139
1. Sign in to your AWS account, go to the Lightsail control panel, and then go to `Containers`
139140
2. Press `create container service` on the top right button
140141
3. Inside the `Create Container Service` page, make sure the available region is automatically selected (usually the region closest to the user)
@@ -143,21 +144,27 @@ Step by step deployment:
143144
6. Press `Create container service`. It will probably take a few minutes.
144145
7. Once you can see the onboarded container in the Lightsail containers dashboard, go to it's `Deployments` section
145146
8. Create a new deployment with the following configuration:
147+
146148
```commandline
147149
Container name: ci-jobs-trigger
148150
Image: quay.io/redhat_msi/ci-jobs-trigger
149151
```
152+
150153
Add the following environment variables:
151-
```
154+
155+
```commandline
152156
[Key]:[Value]
153157
FLASK_DEBUG: 1
154158
CI_JOBS_TRIGGER_LISTEN_IP: 0.0.0.0
155159
```
160+
156161
Open ports:
157-
```
162+
163+
```commandline
158164
[Port]:[Protocol]
159165
5000: HTTP
160166
```
167+
161168
9. Add a public endpoint corresponded to the container name, and change the Health check path to: `/healthcheck`
162169
10. Hit `Save and deploy` and once the deployment is active, you're set to go!
163170

@@ -167,8 +174,11 @@ See a doc about deploy [Flask apps on AWS Lightsail](https://aws.amazon.com/tuto
167174
### Verify the running app
168175

169176
For verify the app is working, make sure you:
177+
170178
- Set the server url path in Vault to the containers domain, should be something similar to:
171-
```
179+
180+
```commandline
172181
https://mpiit-ci-jobs-trigger.<identifier>.<aws-zone>.cs.amazonlightsail.com/openshift-ci-re-trigger
173182
```
183+
174184
- Manually trigger the job `periodic-ci-rhpit-interop-tests-main-retrigger-poc-failure-test` using the gangway api. The job will send a Slack verification of the working app.

0 commit comments

Comments
 (0)