Web Extension Migration
Resource Groups
- [x] Configure webpack for each extension https://github.com/microsoft/vscode-azuretools/issues/1353
- [x] Migrate remaining track 1 packages to track 2
- [x] Identify the Azure SDK packages that need to be migrated to track 2.
- [x] Polyfill or substitute any non-polymorphic dependencies and sub-dependencies
- [x] Migrate from Azure Account extension authentication to VS Code auth provider
- [x] Port over old implementation of VS Code auth provider https://github.com/microsoft/vscode-azureresourcegroups/pull/528
- [x] Refactor Resources to use VS Code auth provider on
UIKind.Webonly https://github.com/microsoft/vscode-azureresourcegroups/pull/542
- [x] Configure a delivery DevOps pipeline for web extensions
- [x] Create a pipeline that can deliver vsix to a public storage blob
- [x] Discern which features are incompatible in the vscode.dev environment
https://github.com/microsoft/vscode-azureresourcegroups/issues/543
- [ ] Refactor extension code into browser, Node.js, and common parts
- [ ] Decrease size of extensions vsixes
Reference for migration path: https://code.visualstudio.com/api/extension-guides/web-extensions
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
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:

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:
It still comes in as a .zip file though. I wonder if that's something that's configurable.
Rough Schedule for the above:
- Configure webpack for each extension: 2 weeks
- Migrate remaining track 1 packages to track 2: 2 weeks
- Polyfill or substitute any non-polymorphic dependencies and sub-dependencies: TBD (Highly variable)
- Migrate from Azure Account extension authentication to VS Code auth provider - 4 weeks
- Configure a delivery DevOps pipeline for web extensions - 3 weeks
- Discern which features are incompatible in the vscode.dev environment - 3 weeks (with workaround)
- Decrease size of extensions vsixes - 3 weeks
| 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!
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
Basically all of this work will be closed by: https://github.com/microsoft/vscode-azureresourcegroups/pull/611
Looks like this extension still declares a dependency on "Azure Account" extension, which is deprecated.
@ggirard07 It's the other way around--Azure Account depends on this extension.
dam it, sorry for bothering :sweat: