This is from telemetry data:

2017-09-15T06:51:08.839Z
vscode-azureappservice/WebAppCreatorError

step
Select or create App Service Plan

error
{"Error":"Error","Message":"Cannot read property 'trim' of null"}

It seems somehow the value passed to the validation handler can be null. Should handle that case.

The publisher value should be "ms-azuretools".

The Start/Stop/Restart context menu for web apps should also show and work for deployment slots.

All of my apps do not appear in the quick pick prompt. At the cited lines, it is checking for Linux and app, however my app appears to only have 'app' in its kind field instead of 'app,linux'

https://github.com/Microsoft/vscode-azureappservice/blob/b5b415525d5195c6696e007234fddbd1854aa417/src/webAppZipPublisher.ts#L175-L176

Per discussion with @chrisdias, the subscription Quick Pick should only show selected subscriptions instead of all subscriptions.

the bash script that gets created has a hard coded cdias-appname-site.git in the comments:

# git remote add azure "https://$USERNAME@$SITENAME.scm.azurewebsites.net/cdias-appname-site.git"

we should be able to use $SITENAME instead:

# git remote add azure "https://$USERNAME@$SITENAME.scm.azurewebsites.net/$SITENAME.git"

use the color icons, or at least make it an option in settings. It is hard to tell what they are otherwise.

If the site name (eventually it is a DNS name, so it is global, not just with subscription) already exists, the creation will fail. Error message is readable but it is still necessary to do the check. Maybe by trying to resolve the DNS name?

Right clicking on a subscription should have a context menu item "Create new Web App", and the "create wizard" will start from prompting resource groups instead of subscriptions because of the context.

Adds a new command -
Azure App Service: Create

The command will prompt for a bunch of inputs to fill up the necessary parameters for creating a new Web App.

We allow stopping, starting, etc. But we can't tell if the service is running or stopped right now. Add a state indicator.

Currently when we load data (subscriptions, apps) we load all of them at once. Should consider optimizing it: caching, background pre-loading, and "Load more..."

Currently we get all subscriptions by ourselves, should now switch to use the subscription filtering provided by the Azure Account extension.

If only one subscription is in the filter setting, then the TreeView should not show the subscription as a top level node, instead the Web Site nodes shall be top level.

If more than one subscriptions are in the filter setting, then Web Sites shall be grouped under subscription nodes.

The input box should have the same behavior as the quick pick - do not cancel when user click away.

After the "Create new Web App" wizard is through, generate a shell script and open it in a new text document editor so users can reuse it.

... and they should be.

Currently the only option is to refresh the root nodes (and collapsing them). Uses shall be able to right click on individual nodes and specifically refresh the selected one and its children if any.

Today we have the key and value in the same node separated by a colon. I propose we display the value as a child node of the key for a few reasons:

1. If the key and/or value has a colon it can be hard to distinguish where one starts and the other ends
   
2. People often put secrets in application settings. This way they could look at all of their keys and individually show/hide the value as desired.
3. I see users changing values more often than keys. I was actually suprised when I clicked 'edit' and the key popped up. This way we could have an edit action on each node with only one input box each.

If Azure Token credentials expire or are altered, the Loading . . . node never resolves and there is no indication that it is not Loading.

A refresh will bring the Sign into Azure. . . node.

Repro steps:

1. Expand a web app
2. Click Refresh on 'Deployment Slots'

Expected: Just the deployment slots node is refreshed
Actual: The entire explorer is refreshed

When I start the process of creating a site I am prompted with a set of quick pick questions (resource group, location, etc.). If at any time I click away from the quick pick box, the quick pick box goes away and i have to start the whole process over again.

You can make the quick pick not go away by setting the quickPickOptions.ignoreFocusOut to True.

Looking at the code, the easiest solution may be to add this to src/wizard.ts in the showQuickPick method. Simply add options.ignoreFocusOut = true before the invocation of showQuickPick:

    async showQuickPick<T>(items: QuickPickItemWithData<T>[] | Thenable<QuickPickItemWithData<T>[]>, options: vscode.QuickPickOptions, token?: vscode.CancellationToken): Promise<QuickPickItemWithData<T>> {
        
        options.ignoreFocusOut = true;
        const result = await vscode.window.showQuickPick(items, options, token);

        if (!result) {
            throw new UserCancelledError();
        }

        return result;
    }

But, I'll leave it up to you if that is the correct place in the code base :)

Also requested by @lostintangent

In addition to deployment via zip, we should support setting up a CI/CD pipeline in Azure/VSTS.

Just thought it might be nice to include something like "1 Core, 1.75 GB RAM" in each pricing tier description. By itself, 'S1' and 'Standard' doesn't mean much to me

If two web apps are part of the same resource group, the deployment slots node shows every slot for that entire resource group instead of only its deployment slots

When a new web app has been created, the wizard should ask something like "do you want to deploy your project to now?" and if the answer is yes, invoke the deployment wizard.

If a WebJob is created in a Deployment Slot, it is not displayed with the web app's WebJobs

The refresh happens before the portal can actually delete the resource so the deleted app/slot is still present on the explorer after the refresh.

Solution: Check the progress of the delete before calling a refresh on the parent node.

Kudu server side 502

Currently you can only deploy a folder that is in the active directory. Should we implement it so that the current directory can also be zipped and deployed?

When loading data from Azure, we should show Quick Pick immediately with progress indicator instead of waiting for data being loaded then show Quick Pick.

Show the name of the functions in the function app. we cant see them now,

after creation of a site i get a nice bash script, but it is named untitled-1.

while the mime type is set correctly (bash script), i suggest giving the file a name such as deploy.sh, much in the same way as the cosmosdb extension creates a results.json file.

Deployment Slot (delete with confirmation)
Web App (deep link to portal delete)

For example, the commands in the App Service node context menu, when called directly from the command palette, don't do anything currently. The correct behavior should be a quick pick list of available App Services so the user can pick which one to execute the command against.

Add FilesNodes back when the node can tell a full end-to-end user story.

The extension shall allow the users to view and edit web app settings.

Currently the app service view show both Windows & Linux web apps and there is no UI indication of the type of the app.

The Cosmos DB extension has a 'showExplorer' setting. The App Service extension should do something similar.

https://github.com/Microsoft/vscode-cosmosdb/blob/master/package.json#L273

This needs support from the Azure Account extension:
microsoft/vscode-azure-account#23

Current "Create New Web App" wizard has too many prompts, we should consider have a "Quick Create" alternative so users can create a new web app after answering two or three prompts.

Or, the extension should have settings that remember certain default settings, for example, the Node.js version, so it won't prompt each time a user wants to create a new web app.