You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We copied the files to storage account using Azure File Copy V6. However it is not generating SASToken.
We need to use this SASToken in the subsequent tasks.
Environment type (Please select at least one enviroment where you face this issue)
Self-Hosted
Microsoft Hosted
VMSS Pool
Container
Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
No response
Operation system
Windows Server 2022
Relevant log output
The output variable is not generating the SAS Token and we cannot use it in the subsequent tasks
Full task logs with system.debug enabled
No response
Repro steps
No response
The text was updated successfully, but these errors were encountered:
@Veera-kambham V6 of the task discourages the use of secrets and encourages the use of Azure RBAC, and therefore no longer generates & uses SAS tokens.
If you need a SAS token in a pipeline, you can create one in the AzureCLI@2 task with az storage account generate-sas or the AzurePowerShell@5 task with New-AzStorageContainerSASToken.
v-snalawade
changed the title
[REGRESSION]: Azure File Copy V6 is not generating SASToken
[Question]: Azure File Copy V6 is not generating SASToken
May 28, 2024
New issue checklist
Task name
Azure File Copy
Breaking task version
6.0
Last working task version
3.0
Regression Description
We copied the files to storage account using Azure File Copy V6. However it is not generating SASToken.
We need to use this SASToken in the subsequent tasks.
Environment type (Please select at least one enviroment where you face this issue)
Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
No response
Operation system
Windows Server 2022
Relevant log output
The output variable is not generating the SAS Token and we cannot use it in the subsequent tasks
Full task logs with system.debug enabled
No response
Repro steps
No response
The text was updated successfully, but these errors were encountered: