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: README.md
+10-10
Original file line number
Diff line number
Diff line change
@@ -72,13 +72,13 @@ The bot is configured entirely via environment variables. You'll want to set up
72
72
73
73
-`LOOKER_URL` (required) – The web url of your Looker instance.
74
74
75
-
-`LOOKER_API_BASE_URL` (required) – The API 3.0 endpoint of your Looker instance. In most cases, this will be the web url followed by `:19999/api/3.0` (replace `19999` with your `core_port` if it is different).
75
+
-`LOOKER_API_BASE_URL` (required) – The API endpoint of your Looker instance. In most cases, this will be the web url followed by `:19999/api/4.0` (replace `19999` with your `core_port` if it is different).
76
76
77
-
-`LOOKER_API_3_CLIENT_ID` (required) – The API 3.0 client ID for the user you want the bot to run as. This requires creating an API 3.0 user or an API 3.0 key for an existing user in Looker.
77
+
-`LOOKER_API_CLIENT_ID` (required) – The API client ID for the user you want the bot to run as. This requires creating an API user or an API key for an existing user in Looker.
78
78
79
-
-`LOOKER_API_3_CLIENT_SECRET` (required) – The API 3.0 client secret for the user you want the bot to run as. This requires creating an API 3.0 user or an API 3.0 key for an existing user in Looker.
79
+
-`LOOKER_API_CLIENT_SECRET` (required) – The API client secret for the user you want the bot to run as. This requires creating an API user or an API key for an existing user in Looker.
80
80
81
-
-`LOOKER_CUSTOM_COMMAND_SPACE_ID` (optional) – The ID of a Space that you would like the bot to use to define custom commands. [Read about using custom commands in the Looker Help Center](https://help.looker.com/hc/en-us/articles/360023685434-Using-Lookerbot-for-Slack).
81
+
-`LOOKER_CUSTOM_COMMAND_FOLDER_ID` (optional) – The ID of a Folder that you would like the bot to use to define custom commands. [Read about using custom commands in the Looker Help Center](https://help.looker.com/hc/en-us/articles/360023685434-Using-Lookerbot-for-Slack).
82
82
83
83
-`LOOKER_WEBHOOK_TOKEN` (optional) – The webhook validation token found in Looker's admin panel. This is only required if you're using the bot to send scheduled webhooks.
84
84
@@ -145,19 +145,19 @@ If you would like the bot to connect to multiple instances of Looker, then you c
145
145
The JSON objects should have the following keys:
146
146
147
147
-`url` should be the web url of the instance
148
-
-`apiBaseUrl` should be the API 3.0 endpoint
149
-
-`clientID` should be the API 3.0 client ID for the user you want the bot to run as
150
-
-`clientSecret` should be the secret for that API 3.0 key
151
-
-`customCommandSpaceId` is an optional parameter, representing a Space that you would like the bot to use to define custom commands.
148
+
-`apiBaseUrl` should be the API endpoint
149
+
-`clientID` should be the API client ID for the user you want the bot to run as
150
+
-`clientSecret` should be the secret for that API key
151
+
-`customCommandFolderId` is an optional parameter, representing a Folder that you would like the bot to use to define custom commands.
152
152
-`webhookToken` is an optional parameter. It's the webhook validation token found in Looker's admin panel. This is only required if you're using the bot to send scheduled webhooks.
153
153
154
154
Here's an example JSON that connects to two Looker instances:
The `LOOKER_URL`, `LOOKER_API_BASE_URL`, `LOOKER_API_3_CLIENT_ID`, `LOOKER_API_3_CLIENT_SECRET`, `LOOKER_WEBHOOK_TOKEN`, and `LOOKER_CUSTOM_COMMAND_SPACE_ID` variables are ignored when `LOOKERS` is set.
160
+
The `LOOKER_URL`, `LOOKER_API_BASE_URL`, `LOOKER_API_CLIENT_ID`, `LOOKER_API_CLIENT_SECRET`, `LOOKER_WEBHOOK_TOKEN`, and `LOOKER_CUSTOM_COMMAND_FOLDER_ID` variables are ignored when `LOOKERS` is set.
0 commit comments