Octokit proxy configuration
See original GitHub issueI have an enterprise github setup which is behind a proxy. Octokit
supports this configuration but there is no notion to pass proxy configuration in @sementic-release/github
library.
Am I missing something?
I have tested this by changing the Octokit
initialization in the following line (It works!):
https://github.com/semantic-release/github/blob/master/lib/get-client.js#L105
Issue Analytics
- State:
- Created 5 years ago
- Comments:8 (3 by maintainers)
Top Results From Across the Web
Module: Octokit::Configurable —
Configuration options for Client, defaulting to values in Default ... Instruct Octokit to get credentials from .netrc file. ... URI for proxy server....
Read more >rest.js - @octokit/rest - npm
Start using @octokit/rest in your project by running `npm i @octokit/rest`. ... such as custom SSL certificate or proxy settings.
Read more >actions/github/README.md - UNPKG
Returns an authenticated Octokit client that follows the machine [proxy settings](https://help.github.com/en/actions/hosting-your-own-runners/using-a-proxy- ...
Read more >HttpClient - Octokit.net Documentation - Read the Docs
If you want to understand more of the internals of how Octokit is using ... There's some basic support for specify proxy credentials,...
Read more >Octokit NPM - npm.io
Proxy Servers (Node.js only). By default, the Octokit API client does not make use of the standard proxy server environment variables. To add...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
The fact that the target URL is
https
is independent of the protocol supported by the proxy. You can use anhttp
proxy to reach anhttps
URL and vice-versa. The environment variableHTTP_PROXY
is just a generic name, it doesn’t imply that the proxy has to be contacted withhttp
orhttps
nor that the URL you target ishttp
orhttps
.You should configure
HTTP_PROXY
tohttps://your-proxy:3128
if it supportshttps
and you want the communications between the plugin and the proxy to be secured. If your proxy doesn’t supporthttps
or you don’t want to secure the communication between between the client and the proxy then you can configureHTTP_PROXY
tohttp://your-proxy:3128
.thanks, @pvdlg for the explanation.