question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Documentation: AzureFileCopyV4 output variable documentation incomplete

See original GitHub issue

Required Information

Entering this information will route you directly to the right team and expedite traction.

Question, Bug, or Feature?
Type: Bug

documentation issue

Enter Task Name: AzureFileCopyV4

list here (V# not needed):
https://github.com/microsoft/azure-pipelines-tasks/tree/master/Tasks/AzureFileCopyV4

Environment

  • Server - Azure Pipelines

    • If using Azure Pipelines, provide the account name, team project name, build definition name/build number: n/a
  • Agent - Hosted or Private:

    • If using Hosted agent, provide agent queue name: windows-latest

Issue Description

The AzureFileCopyV4 task has poor documentation on working with its output variables. In v3, the variables outputted were task inputs. In v4, they are created as output variables (and not defined in the task ui). The documentation between v3 and v4 does not change in any way to reflect this.

You have to know to dig into the task code to find out that the output variables are titled:

  • StorageContainerUri
  • StorageContainerSasToken

Following the output variables documentation, we can then reference the variables like so:

- task: AzureFileCopy@4
  inputs:
    SourcePath: 'Readme.md'
    azureSubscription: 'Test'
    Destination: 'AzureBlob'
    storage: 'azdo'
    ContainerName: 'workshops'
    BlobPrefix: ''
  name: AzureFileCopy
- script: | 
    echo $(AzureFileCopy.StorageContainerUri)
    echo $(AzureFileCopy.StorageContainerSasToken)

I can submit a PR for the readme update if desired. Thanks

Task logs

N/a

Troubleshooting

n/a

Error logs

n/a

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:5 (4 by maintainers)

github_iconTop GitHub Comments

1reaction
20shivangicommented, Sep 30, 2020

Closing this issue as documentation PR is merged

1reaction
jashanbhullarcommented, Jul 19, 2020

@soccerjoshj07 Thank you for this. Been beating my head at this for the whole day 👍

Read more comments on GitHub >

github_iconTop Results From Across the Web

AzureFileCopy@4 - Azure file copy v4 task | Microsoft Learn
In this article. Syntax; Inputs; Output variables; Remarks; Examples; Requirements. Copy files to Azure Blob Storage or virtual machines.
Read more >
AzureFileCopy@4 task to copy to Azure Blob storage unable ...
We are using windows-2019 hosted agents. Although not clearly documented in these docs per info found on the web, at the storage account,...
Read more >
using AzureFileCopy task outputs in Azure-Pipelines.yml
Kind of related but if you are using V4 then these are available as Output Variables. This is not there in the documentation...
Read more >
Automating Snowpipe for Microsoft Azure Blob Storage
Click the Review + assign button. Note. According to the Microsoft Azure documentation, role assignments may take up to five minutes to propagate....
Read more >

github_iconTop Related Medium Post

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found