Docker@1 task has bad enum for `command` about azure-pipelines-vscode HOT 6 CLOSED

I think this is working correctly @vtbassmatt. The only Task I see that has weird values is AzureVmssDeployment@0. Going to close, please reopen if you think otherwise.

from azure-pipelines-vscode.

Is the Docker@1 task also doing it wrong? https://github.com/Microsoft/azure-pipelines-tasks/blob/13e7e7be3fd7a68cd30634436a3826ca5b084d1a/Tasks/DockerV1/task.json#L88

from azure-pipelines-vscode.

Looks like Docker@1 does it wrong, but you were going to take another quick look.

from azure-pipelines-vscode.

AzureAppServiceManage
AzureResourceGroupDeploymentV2
AzureRmWebAppDeploymentV3
AzureRmWebAppDeploymentV4
AzureVmssDeploymentV0
DockerComposeV0
DockerV0
DockerV1
HelmDeployV0
KubernetesV0
KubernetesV1
ServiceFabricUpdateManifestsV2

I think some of these are tasks copied from previous tasks doing it wrong. I am going to file bugs for all of them and will link here.

from azure-pipelines-vscode.

Thanks. I think you're right that we shouldn't make a change in the task schema generation for this. Should we file bugs on those tasks do something more sensible in the future?

from azure-pipelines-vscode.

Yeah we can't change the schema since it then wouldn't match on the server.

Good question, I was going to but let's discuss tomorrow morning.

from azure-pipelines-vscode.