microsoft / microsoft/vscode-azurestaticwebapps

Publish a SWA from VS Code

Open
#265 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

tracking
Dominant language
TypeScript
Stars
99
Forks
39
Avg merge
3d 7h
Merged PRs (30d)
2

Description

Needs discussion

  1. Select a SWA (exclude ones that are connected to GitHub):
    • Create a SWA without connecting to GitHub
    • Or select from list of SWAs not connected to GitHub
  2. Select a storage account and blob container (must be private) - Currently, the deployment API takes a URL to a zip file so a Storage account is needed. Need to figure out the most seamless experience here to ensure one exists and to select it.
  3. Select frontend app output/artifacts location
  4. Select backend app location (do we build the app for them? what if it's an app like C# that builds into a subdirectory?)

Then the extension will zip up the 2 folders in the right format and upload it to the container. Generate a SAS URI for the file and call the zipdeploy API with the SAS URI.

When successful, do we delete the file from storage?

/cc @miwebst @annaji-msft

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points. Start by mapping the extension's existing SWA publishing flow, then resolve the open decisions around resource selection, build locations, storage handling, SAS upload, and cleanup before implementation. Done means the complete VS Code workflow is defined and successfully publishes both frontend and backend artifacts.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, typescript, vscode
Domain
cloud, devtools
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.