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
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Bug Report
Error Description
Creating a custom domain behind a HTTP proxy fails.
Command Run sls deploy
Console Output
Error --------------------------------------------------
Error: Error: Unable to setup base domain mappings for (obfuscated)
at ServerlessCustomDomain.<anonymous> (/app/node_modules/serverless-domain-manager/dist/index.js:164:27)
at Generator.throw (<anonymous>)
at rejected (/app/node_modules/serverless-domain-manager/dist/index.js:6:65)
at processTicksAndRejections (internal/process/task_queues.js:97:5)
For debugging logs, run again after setting the "SLS_DEBUG=*" environment variable.
Domain Manager Configuration
Replace this with your own serverless.yml file (anonymized, of course) to help us better resolve your issue.
Reverting to 4.2.0 resolved the issue. It seems this recent change has changed the CloudFormation provider not to inherit from the Serverless configured AWS SDK.
Serverless Framework is responsible for passing a proxy-agent through to the SDK and configuring this according to the proxy specified in HTTP_PROXY etc. It seems this approach was originally proposed in #86 & implemented in #89.
Additional context/Screenshots
The attempt to make a CloudFormation API call was the only one to fail - all other steps in the deployment succeeded. This aligns with the recent change in #380 to refactor the CloudFormation client.
The text was updated successfully, but these errors were encountered:
Community Note
Bug Report
Error Description
Creating a custom domain behind a HTTP proxy fails.
Command Run
sls deploy
Console Output
Domain Manager Configuration
Replace this with your own
serverless.yml
file (anonymized, of course) to help us better resolve your issue.Versions
Possible Solution
Reverting to 4.2.0 resolved the issue. It seems this recent change has changed the CloudFormation provider not to inherit from the Serverless configured AWS SDK.
Serverless Framework is responsible for passing a
proxy-agent
through to the SDK and configuring this according to the proxy specified inHTTP_PROXY
etc. It seems this approach was originally proposed in #86 & implemented in #89.Additional context/Screenshots
![image](https://user-images.githubusercontent.com/594697/93865406-2dc39680-fcbe-11ea-8879-aefc39d66499.png)
The attempt to make a CloudFormation API call was the only one to fail - all other steps in the deployment succeeded. This aligns with the recent change in #380 to refactor the CloudFormation client.
The text was updated successfully, but these errors were encountered: