erick-enriquez-dd opened a new issue, #22442:
URL: https://github.com/apache/superset/issues/22442
A clear and concise description of what the bug is.
When configuring alerts and reports, I am seeing the following error in my
production environment. I used the same exact Slack API token in my staging
environment and had no issues. I have printed the token out in
superset_config.py to verify. Is there some issue with using the same token in
two different instances?
```
| superset [2022-12-17 00:34:00,175: INFO/ForkPoolWorker-31] Scheduling
alert Test2 eta: 2022-12-17 00:34:00 │
│ superset Query for Test2 took 84.05 ms
│
│ superset [2022-12-17 00:34:00,361: INFO/ForkPoolWorker-31] Query for Test2
took 84.05 ms │
│ superset Screenshotting chart at
http://superset:8088/superset/slice/85/?standalone=true
│
│ superset [2022-12-17 00:34:00,372: INFO/ForkPoolWorker-31] Screenshotting
chart at http://superset:8088/superset/slic │
│ superset Init selenium driver
│
│ superset [2022-12-17 00:34:00,375: INFO/ForkPoolWorker-31] Init selenium
driver │
│ superset Taking a PNG screenshot or url
http://superset:8088/superset/slice/85/?standalone=true&standalone=3 │
│ superset [2022-12-17 00:34:11,699: INFO/ForkPoolWorker-31] Taking a PNG
screenshot or url http://superset:8088/supers │
│ superset Report state: The request to the Slack API failed.
│
│ superset The server responded with: {'ok': False, 'error': 'not_authed'}
│
│ superset [2022-12-17 00:34:12,363: INFO/ForkPoolWorker-31] Report state:
The request to the Slack API failed. │
│ superset The server responded with: {'ok': False, 'error': 'not_authed'}
```
- browser type and version: chrome 108
- superset version: `1.3.1`
### Additional context
I configured the environment variable SLACK_API_TOKEN via a helm chart under
the subfield values.superset.supersetNode.env.SLACK_API_TOKEN. This environment
variable is visible when I describe my main superset pod but not visible in
superset-custom-env (it was visible in my staging's version of
superset-custom-env).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
