DevelopmentVM: VS Code not linked to accelerators repo by default about accelerators_accelerateurs-azure

[bernardmaltais]

Hello Graham, I will investigate why that might be the case. Thank you for reporting this.

Bernard

[GrahamAshford]

Thanks Bernard. If there is any logging or otherwise that I can supply you with I would be happy to - please let me know.

Graham

[chadif]

Hi,

I ran a fresh deployment this morning and the repo was linked in VS Code when I first opened it. I did run the InstallVSCExtensions.bat batch file beforehand so not sure if that makes a difference?

Chadi

[bernardmaltais]

I found the issue. It was a bad link to the older template. It should now be fixed. I repointed the deployment to the new github location with new deployment code. All the code got moved to github recently and this was one of the few remaining updates that apparently did not get pushed.

Thank you for bringing this issue up to me chadif. I also saw the work you started to do on your fork to parametrize the baseVM name. I like it. Do not hesitate to submit a pull request when you feel you have something stable.

Bernard

[bernardmaltais]

Also, you will want to update your fork so you make the same change to the readme.md file I did. That way you will point to your own fork when testing deployment.

[chadif]

I actually deployed the template using Azure CLI while providing the exact URI so I think that's why it worked for me! But good point on updating the URL on the readme.md

[GrahamAshford]

Thanks for the quick turnaround folks. I re-deployed and VSCode now has the repo linked. Closing!