Skip to Main Content
Customer Feedback

We love feedback from you on our products and the problems in your daily work that you would like us to solve. Please describe the challenge you're encountering and your desired outcome. Be as detailed as possible.

For technical issues or bugs please head to Support or our Developer Community. You can assign up to 20 votes in total. Thank you for your feedback.

Status explanation: 'Future Consideration' = Continuing to collect further feedback, not planned at this time. 'Investigating' = Prioritized for deeper customer and feasibility investigations ahead of planning development.

Status Future consideration
Categories Code deployment
Created by Guest
Created on Sep 10, 2021

Update EpiCloud PowerShell module to support disabling keep-alive

We are attempting to use the EpiCloud PowerShell module to automate deployments of our Optimizely solution into the Optimizely DXP.

Unfortunately, when we run the command to initiate the deployment, then it fails because HTTP keep-alive failed. The reason for this is our corporate proxy doesn't allow HTTP keep-alive.

Can you update the PowerShell module to include options to disable keep-alive for corporate situations like this?

The command we are running is:

Start-EpiDeployment -DeploymentPackage -TargetEnvironment Integration -DirectDeploy

The error we are getting is:

API call failed! The error was: The underlying connection was closed: A connection that was expected to be kept alive was closed by the server.

It would be similarly helpful to expose other network-related options to help with locked-down network environments, such as disabling TLS validation, bypassing the proxy, or using an alternative proxy.