new-extension-version fails if manifest contains CRLF

[matt-richardson]

I found, through lots of painful trial and error, that if your manifest file has CRLF line endings, it fails when pushing to azure.

It throws on the server side, and returns a 400 with no body.

Replacing CRLF with LF works fine.

(I suspect this is not the right repo for this issue, but not sure where to log. Maybe https://github.com/Azure/azure-marketplace is the right spot?)

[boumenot]

I don't think Azure/azure-marketplace is the correct repo. Let me see if I can connect this issue with the right people.

A couple of questions:

1. Are you using this tool to deploy an extension?
   • If yes, we should be able to sanitize the input before sending it.
2. Are you able to attach or reproduce a minimal repo?