Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Azure File Copy Extended unable set Additional Arguments #57

Open
doggy8088 opened this issue Aug 22, 2021 · 1 comment
Open

Azure File Copy Extended unable set Additional Arguments #57

doggy8088 opened this issue Aug 22, 2021 · 1 comment

Comments

@doggy8088
Copy link

doggy8088 commented Aug 22, 2021

I'm using Azure Pipelines. I'd like to append /SetContentType to the AzCopy command so I configured Additional Arguments field. Here is my config:

image

Here is the YAML version:

steps:
- task: geeklearningio.gl-vsts-tasks-azure.az-copy-task.AzCopy@1
  displayName: 'Copy files from or to Azure Storage'
  inputs:
    SourceKind: FileSystem
    SourcePath: '$(System.DefaultWorkingDirectory)/_QA-CI/drop/site'
    DestinationConnectedServiceName: 'Microsoft Azure Sponsorship'
    DestinationAccount: docs
    DestinationObject: site
    Recursive: true
    ExcludeNewer: false
    ExcludeOlder: false
    Arguments: /SetContentType

Here is the log. I can't see /SetContentType in the command:

2021-08-22T03:24:15.1293251Z [command]C:\agents\2.190.0\externals\azcopy\azcopy.exe /Source:D:\a\r1\a\_QA-CI\drop\site /Dest:https://mystor.blob.core.windows.net/site /DestKey:****** /S /Y

I saw the source. It seems okay. I don't know why I can't add Additional Arguments to the command.

if (additionalArguments) {
toolRunner.line(additionalArguments);
}

I already tried many ways. I never have a chance to add additional arguments to the AzCopy command.

Is this a bug or what's missing from me?

@doggy8088 doggy8088 changed the title AzCopy V2 unable set Additional Arguments Azure File Copy Extended unable set Additional Arguments Aug 22, 2021
@davidmiguelalves
Copy link

Hi, this is going to be fixed? I notice than the arguments is comming undefined:

2022-02-07T12:50:52.0149190Z ##[debug]Arguments=undefined

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants