-
Notifications
You must be signed in to change notification settings - Fork 159
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 Configuration is broken in v8 #1004
Comments
Hi @jonask94, |
Hi @kushalshit27 , Unfortunately I'm still getting the same error with v8.4.3:
|
Hi, @jonask94 , |
Hi @jonask94 |
Hi @kushalshit27 With the
|
Checklist
Description
We are using the auth0-deploy-cli in our CI/CD-process.
The automated import to our staging tenants is executed behind a proxy.
Therefore we have to use the
--proxy_url
configuration, which worked fine in the past.We just updated the deploy-cli to the newest major-version v8.
With v8 the proxy configuration seems to be broken.
The deploy-cli is not able to authenticate or to do any requests:
FetchError: The request failed and the interceptors did not return an alternative response
(Without the proxy-configuration the import works as expected)
As far as I understood from the changelogs and migration guides, this behaviour could be caused by migrating to
node-auth0/v4
.At least I found a change regarding the proxy configuration here: https://github.com/auth0/node-auth0/blob/master/v4_MIGRATION_GUIDE.md#authentication-api
Expectation
auth0-deploy-cli should be able to work with
--proxy_url
configuration in v8Reproduction
--proxy_url=http://sample.proxy:port
Deploy CLI version
8.4.1
Node version
20.18.0
The text was updated successfully, but these errors were encountered: