Deployments fail if application name has a space in it
See original GitHub issueIf my Elastic Beanstalk application has a space in its name, e.g. “Application Name”, and I attempt to run your script then I get the following errors:
Deployment failed: TypeError [ERR_UNESCAPED_CHARACTERS]: Request path contains unescaped characters
Do you reckon you can fix that?
Issue Analytics
- State:
- Created 3 years ago
- Comments:10 (6 by maintainers)
Top Results From Across the Web
Variable values containing spaces cause Azure App Service ...
If a variable has a space in it the value is preserved as entered and the deployment continues successfully. Also the string should...
Read more >App Service Deploy: Extra spaces in settings causes ... - GitHub
When you edit the "Application and Configuration settings/App Settings" section, if there's an extra space between key/values the parsing ...
Read more >"extend.spaces.webapp" Failed To Deploy - Oracle Support
Created an ADF taskflow and deployed it as a shared library to WC_PORTAL server. After registering the library to a WebCenter Portal extension ......
Read more >Deployments | JetBrains Space Documentation
If, for some reason, the deployment script fails, you can fail the deployment as well, i.e. change its status to failed. A deployment...
Read more >Troubleshoot specific errors in ClickOnce deployments
This article describes common errors that can occur when you deploy a ClickOnce application and provides steps to resolve each problem.
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 FreeTop 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
Top GitHub Comments
The issue still persists but I fixed it by removing the spaces in the application name. May be worth to add a warning somewhere in the README file. Besides that, it does the job flawlessly, thanks a lot.
Finally managed to fix this in v13! Closing this issue!