Skip to content
This repository was archived by the owner on Apr 24, 2023. It is now read-only.

Commit 4b0dadd

Browse files
authored
Merge pull request #27 from integr8ly/INTLY-7031
Intly 7031
2 parents 4a072c0 + ea3a31a commit 4b0dadd

File tree

2 files changed

+33
-11
lines changed

2 files changed

+33
-11
lines changed

hidden_walkthroughs/3-low-code-api-development/walkthrough.adoc renamed to walkthroughs/3-low-code-api-development/walkthrough.adoc

Lines changed: 33 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -145,7 +145,15 @@ greetname
145145

146146
. In the *REQUEST BODY* section, select the *Add a request body* link.
147147

148-
. For the *Request Body Type*, select *Name*. This is the type you created earlier.
148+
. In the dropdown, select the *Required* option.
149+
150+
. Select the *Add a media type* link.
151+
152+
. Make sure *application/json* is selected and click *Add*.
153+
154+
. Select a type for your request by clicking on the *> No Type* column under *Media Types*
155+
156+
. Select *Name* from the dropdown.
149157
+
150158
NOTE: The drop-down may look inactive. Just click it and you should have the option to select "Name".
151159

@@ -156,15 +164,14 @@ NOTE: The drop-down may look inactive. Just click it and you should have the opt
156164
----
157165
Greeting response
158166
----
159-
.. For the *Response Type*, click *Choose Type* and then select *String*. You will then see an additional drop-down displayed, with the *Type* now showing "*String* as *String*".
167+
.. Select the *Add a media type* link.
168+
.. In the dropdown, select the *text/html* option and click on *Add*.
169+
.. Click on the *> No type* column and select *String* from the dropdown. You will then see an additional drop-down displayed, with the Type now showing "String as String".
160170

161171
=== Export the OpenAPI Spec as JSON/YAML
162172

163173
. On the top right of the screen, click the *angle down icon* next to the *Save As...* button.
164174
. Select *Save as YAML*.
165-
. On the top right of the screen, click the *Close* button.
166-
. You will see a modal asking you to "Save changes before closing?", so click *Save*.
167-
168175
+
169176
NOTE: Keep this file safe. It will be used to create the API implementation in Fuse Online shortly.
170177

@@ -236,10 +243,25 @@ You are redirected back to the *Incoming Webhooks* page.
236243
.. Copy the *Webhook URL* displayed at the bottom of the page using the *Copy* button.
237244
. Paste the copied *Webhook URL* value into the *Slack Webhook URL* field in Fuse Online.
238245
. Obtain a value for the *Token for Accessing Slack API* field:
239-
.. Go to the Slack API Token portal at link:https://api.slack.com/custom-integrations/legacy-tokens[api.slack.com/custom-integrations/legacy-tokens, window="_blank", id="{context}-6"].
240-
.. Scroll down to the *Legacy token generator* section.
241-
.. Click *Create token* button next to *low-code-workspace*.
242-
.. Copy the generated token.
246+
.. Go to *OAuth & Permissions* in the Slack API portal.
247+
.. Scroll down to the *Scopes* section.
248+
.. Under *Bot Token Scopes* click on the *Add an OAuth Scope* button, or if visible, inside the *Add permission by Scope or API method...* field.
249+
.. Add the *channels:read* permission.
250+
.. Click on the *Add an OAuth Scope* button again to add the *chat:write* permission.
251+
+
252+
NOTE: A notification should appear instructing you to reinstall the app.
253+
254+
[type=verification]
255+
Look at the Bot Token Scopes. Do you see OAuth Scopes listed for *channels:read*, *chat:write* and *incoming-webhook*?
256+
257+
[type=verificationFail]
258+
Go back to section *7* and add the missing scopes.
259+
260+
=== Obtaining the OAuth access token for Slack
261+
262+
. Scroll up and click on the *Reinstall App* button.
263+
.. Next you need to confirm the new permissions. Select *low-code-workspace* from the dropdown and click on *Allow*.
264+
.. Now you can copy the generated token under *Bot User OAuth Access Token*.
243265
. Paste the generated token into the *Token for Accessing Slack API* field in Fuse Online.
244266
. Enter the following in the *Sending User Name for Messages* field:
245267
+
@@ -348,8 +370,8 @@ By default, Fuse Online does not expose an *Integration* to the public internet
348370
=== Find the Greeting Service Internal Hostname
349371

350372
. Login to the link:{openshift-console-url}[OpenShift Console, window="_blank"].
351-
. Select the project named with the following format: `redhat-rhmi-fuse`.
352-
. Choose *Network > Services* from the left menu.
373+
. Go to *Home > Projects* and select the project named with the following format: `redhat-rhmi-fuse`.
374+
. Choose *Networking > Services* from the left menu.
353375
. Make sure there is a *i-greeting-integration-{user-username}* item in the *Services* list.
354376
. Take a note of the hostname: `i-greeting-integration-{user-username}.redhat-rhmi-fuse.svc.cluster.local`.
355377

hidden_walkthroughs/3-low-code-api-development/walkthrough.json renamed to walkthroughs/3-low-code-api-development/walkthrough.json

File renamed without changes.

0 commit comments

Comments
 (0)