-
Notifications
You must be signed in to change notification settings - Fork 149
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.
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
Proxy Support broken on Slack App approach (Slack Bot Token approach) #217
Comments
Hello @frednntelia thanks for writing in 💯 This is a curious behavior, would be able to tell me if the proxy you are using is Based on this test suite seems like webhook method |
Hi @WilliamBergamin, thanks for your swift response! 👍🏾 |
@WilliamBergamin is there a way to enable debug level logs from this Action, so that we can get some more context? |
Based on what I can see in the code there seems to be a bug where HTTP proxies are not properly set but HTTPS proxies are, I am not sure if there is a reason behind this |
Is there a plan to release this fix? If not, is there a workaround that can be used in the meantime? |
Description
When using the slack-github-action in GitHub App mode, the Action fails to utilize environment variables
HTTPS_PROXY
andhttps_proxy
correctly.What type of issue is this? (place an
x
in one of the[ ]
)Requirements (place an
x
in each of the[ ]
)Bug Report
Filling out the following details about bugs will help us solve your issue sooner.
Reproducible in:
package version: slackapi/slack-github-action@v1.24.0
node version:
OS version(s): Ubuntu 20.04 LTS
Steps to reproduce:
Expected result:
HTTPS_PROXY var is respected and slack api call goes through properly, resulting in the display of a message on the respective channel.
Actual result:
Slack message never arrives in channel. Likely because HTTPS_PROXY env var is not being respected
Attachments:
The text was updated successfully, but these errors were encountered: