Add scenario for BlobPipe case

Author: dphulkar-msft

azure-pipelines.yml

@@ -480,8 +480,16 @@ jobs:
         workingDirectory: $(Build.ArtifactStagingDirectory)
         condition: eq(variables['agent.os'], 'Windows')
 
-      - template: azurePipelineTemplates/run_scenarios.yml
+      - template: azurePipelineTemplates/run_scenarios_linux_macos.yml
         parameters:
-          build_name: $(Build.ArtifactStagingDirectory)/drop/$(build_name)
+          build_name: $(build_name)
           container_name: $(container_name)
           storage_account_name: $(AZCOPY_E2E_ACCOUNT_NAME)
+        condition: or(eq(variables['agent.os'], 'Linux'), eq(variables['agent.os'], 'macOS'))
+        
+      - template: azurePipelineTemplates/run_scenarios_windows.yml
+        parameters:
+          build_name: $(build_name)
+          container_name: $(container_name)
+          storage_account_name: $(AZCOPY_E2E_ACCOUNT_NAME)
+        condition: eq(variables['agent.os'], 'Windows')

azurePipelineTemplates/run_scenarios.yml renamed to azurePipelineTemplates/run_scenarios_linux_macos.yml

@@ -17,6 +17,8 @@ steps:
         # Right now we dont have this fix available in the older version of AzCopy. So, we are using the latest version of AzCopy to run the scenarios.
         # We will update this workaround once the fix is available in the older version of AzCopy.
 
+        export AZCOPY_AUTO_LOGIN_TYPE=AzCLI
+
         ${{ parameters.build_name }} make "https://${{ parameters.storage_account_name }}.blob.core.windows.net/${{ parameters.container_name }}"
         echo "Hello, Azure!" > myfile.txt
         ${{ parameters.build_name }} cp myfile.txt "https://${{ parameters.storage_account_name }}.blob.core.windows.net/${{ parameters.container_name }}"

azurePipelineTemplates/run_scenarios_windows.yml

@@ -0,0 +1,31 @@
+parameters:
+  - name: build_name
+    type: string
+  - name: storage_account_name
+    type: string
+  - name: container_name
+    type: string
+
+steps:
+  - task: AzureCLI@2
+    inputs:
+      azureSubscription: azcopyTestScenarios
+      addSpnToEnvironment: true
+      scriptType: pscore
+      scriptLocation: inlineScript
+      inlineScript: |
+        # Right now we dont have this fix available in the older version of AzCopy. So, we are using the latest version of AzCopy to run the scenarios.
+        # We will update this workaround once the fix is available in the older version of AzCopy.
+
+        $env:AZCOPY_AUTO_LOGIN_TYPE = "AzCLI"
+        & "$(Build.ArtifactStagingDirectory)\drop\$(${{ parameters.build_name }})" make "https://${{ parameters.storage_account_name }}.blob.core.windows.net/${{ parameters.container_name }}"
+        echo "Hello, Azure!" > myfile.txt
+        & "$(Build.ArtifactStagingDirectory)\drop\$(${{ parameters.build_name }})" cp myfile.txt "https://${{ parameters.storage_account_name }}.blob.core.windows.net/${{ parameters.container_name }}"
+        & "$(Build.ArtifactStagingDirectory)\drop\$(${{ parameters.build_name }})" cp "https://${{ parameters.storage_account_name }}.blob.core.windows.net/${{ parameters.container_name }}/myfile.txt" --from-to=BlobPipe --check-md5 FailIfDifferentOrMissing > filename
+        # Check if the command succeeded
+        if ($LASTEXITCODE -eq 0) {
+          Write-Output "AzCopy command succeeded."
+        } else {
+          Write-Error "AzCopy command failed with exit code $LASTEXITCODE."
+        }
+    displayName: 'Run Scenarios to check if older version of AzCopy appends version check error message to piped download'