search

microsoft / vscode-azureresourcegroups

VS Code extension for managing Azure resources.
https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-azureresourcegroups
MIT License
47 stars 29 forks source link

Web Extension Migration #512

Open nturinski opened 1 year ago

nturinski commented 1 year ago

Resource Groups

Reference for migration path: https://code.visualstudio.com/api/extension-guides/web-extensions

bwateratmsft commented 1 year ago

Potentially useful, the Dev CLI extension has some pipeline config that will create, publish, and comment with a link to the VSIX on PRs. Like so: https://github.com/Azure/azure-dev/pull/853#issuecomment-1375937535

alexweininger commented 1 year ago

Potentially useful, the Dev CLI extension has some pipeline config that will create, publish, and comment with a link to the VSIX on PRs. Like so: Azure/azure-dev#853 (comment)

That's really nice.

If we also migrated our pipelines to GitHub Actions, we'd wouldn't have to leave GitHub to DevOps as often. See Python extension for example https://github.com/microsoft/vscode-python/actions/runs/3894486696

It has the artifacts at the bottom:

image
nturinski commented 1 year ago

Potentially useful, the Dev CLI extension has some pipeline config that will create, publish, and comment with a link to the VSIX on PRs. Like so: Azure/azure-dev#853 (comment)

That's really nice.

If we also migrated our pipelines to GitHub Actions, we'd wouldn't have to leave GitHub to DevOps as often. See Python extension for example https://github.com/microsoft/vscode-python/actions/runs/3894486696

It has the artifacts at the bottom: image

It still comes in as a .zip file though. I wonder if that's something that's configurable.

meeraharidasa commented 1 year ago

Rough Schedule for the above:

<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns="http://www.w3.org/TR/REC-html40">

PM/Eng | Work | Weeks | Date -- | -- | -- | -- Nathan | Configure webpack for each extension | 1 weeks | ~ 1/27 Nathan | Migrate remaining track 1 packages to track 2: | 2 weeks | ~2/17 Megan & Matthew | Polyfill or substitute any non-polymorphic dependencies and sub-dependencies | 2 weeks |  ~2/17 Meera | Discern which features for Resource Groups is a MUST have by looking at data, verbatims and usage patterns | 2 weeks | ~2/3 Nathan | Discern which features are incompatible in the vscode.dev environment | 2 weeks | ~2/3 Megan & Matthew | Migrate from Azure Account extension authentication to VS Code auth provider | 2 weeks | ~2/17 Nathan | Configure a delivery DevOps pipeline for web extensions | 3weeks | TBD Nathan | Decrease size of extensions vsixes | 4 weeks | TBD

@nturinski please take a look and change whatever I got wrong!

bwateratmsft commented 1 year ago

One thing we need to do; a request to the VSCode team to permit customizing the cloud used for MS auth. i.e. custom clouds and such.

An issue exists already: https://github.com/microsoft/vscode/issues/162539

nturinski commented 1 year ago

Basically all of this work will be closed by: https://github.com/microsoft/vscode-azureresourcegroups/pull/611