Use Variables to specify SecureFile to download in DownloadSecureFile Task

[fume]

Hi,
this is not an issue but just a suggestion about the DownloadSecureFile task.

I think that could be very useful to be able to specify the SecureFile name via a variable, but the "secureFile" type only allows the selection via UI. This will also allow to create parametrized Task groups containing this task.

thanks, regards

[pwil301]

Completely agree with this request. Not being able to use a variable or dynamically select a secure file prevents using the library for some purposes it is otherwise perfectly suited for.

As mentioned here (quote below in case the link goes stale): https://stackoverflow.com/questions/49678831/how-to-use-variable-to-specify-secure-file-input-value-in-tfs-2017u2-build-and-r

"Our workflows include generating new x509 certificates and pushing them into the Secure Files library and setting properties on the entries such as CN, thumbprint, SAN, etc. We then need to pull the file down to an agent for tasks later in the workflow. However, because the file is not in the library at design time, we cannot select it in the list.

We tried implementing a custom download task. However, if you don't use the "securefile" input type and specify the exact file you need when defining the build, TFS won't issue a download ticket to the agent and you thus can't download the actual file (only metadata)."

Any chance for a solution?

[fume]

is there any ETA for this enhancement?

thanks, regards

[DuncanMillard]

+1 request for this

[ericsciple]

This is something we want to enable.

The closest fit today would be conditional tasks or yaml templates. Both requiring knowing the file up front.

[SqlSusan]

Also waiting for this enhancement. Is there a workaround?

[madhurig]

This is supported via yaml but we don't have an ETA on support in the classic designer.

E.g.

[EdwardBlair]

@madhurig This doesn't work if you nest this within a job definition

[fume]

@madhurig still no ETA for the classic designer?

thanks, regards

[johncrim]

This works today - you can use the step name: to provide a secure file variable prefix. Then add .secureFilePath to the prefix for the variable name. The following example works:

- task: DownloadSecureFile@1
  name: CaCert
  displayName: 'Download CA cert'
  inputs:
    secureFile: 'ca.pem'

- script: |
	echo Installing $(CaCert.secureFilePath) to trusted CA directory...
	sudo chown root:root $(CaCert.secureFilePath)
	sudo chmod a+r $(CaCert.secureFilePath)
	sudo ln -s -t /etc/ssl/certs/ $(CaCert.secureFilePath)