Use VSCode proxy settings in git-credential-helper script

[DavideDelbiancoZucchetti]

Is your feature request related to a problem? Please describe.
When working with this extension behind an enterprise proxy, git operations for Alexa's hosted skills will fail.

Describe the solution you'd like
The ideal solution would be for the extension to keep in consideration VSCode proxy settings when generating the git-credential-helper scripts that are saved in %USERPROFILE%\.ask\scripts

Describe alternatives you've considered
I have bypassed the issue by altering every curl call in the scripts adding -x "proxy:port"

[CamdenFoucht]

Hi @DavideDelbianco Thank you for the feature request. We will look into adding this into the extension.

[tydonelson]

Hey @DavideDelbianco , thanks for your patience around this issue! I'm trying to get a better picture of your development environment, when you get a chance could you help me with some more context?

• When you say VSCode proxy settings, where are you setting those and what exactly are you setting? I assume http.proxy in settings.json is a piece of the puzzle for you, but I want to make sure I'm not missing anything you're doing to get things working.
• Are you running into this from "Download and edit skill" in Skills Management, or some other workflow?

Thanks for any information you can provide, we'd like to get this integrated!

[DavideDelbiancoZucchetti]

Hi Tyler, Yes I'm talking about "http.proxy" setting and yes it is a problem with the download and edit skill. It is related to the capability of git or pushing/pulling source code from the Alexa's hosted git repository. The scripts that are generated in the user folder are used by git-credential-manager to obtain a token thru curl calls

[tydonelson]

Hey Davide, thanks for confirming. We're looking at our options here and hope to get it on the roadmap soon.