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

Use secure file name as reference data instead of id #593

Open
1 task
aklakina opened this issue Mar 28, 2024 · 1 comment
Open
1 task

Use secure file name as reference data instead of id #593

aklakina opened this issue Mar 28, 2024 · 1 comment

Comments

@aklakina
Copy link

aklakina commented Mar 28, 2024

  1. Please check our current Issues to see if someone already reported this https://github.com/Microsoft/vsts-node-api/issues
  2. Take a look at our Instructions for logging issues https://github.com/Microsoft/vsts-node-api/blob/master/CONTRIBUTING.md#instructions-for-logging-issues

Environment

Node version: v18.14.0
Npm version: 9.3.1
OS and version: windows 10 22H2
azure-devops-node-api version: 2022.1

Issue Description

When updating a secure file (deleting and then reuploading with the new content with the same name) every classic pipeline breaks that was using that secure file.

Expected behaviour

The classic pipelines should hold the reference for the new secure file.

Actual behaviour

The classic pipelines referencing the old secure file break.

Steps to reproduce

This issue is strongly related to microsoft/azure-pipelines-tasks-common-packages#309

  1. upload secure file
  2. create classic pipeline with a secure file download task
  3. set the secure file created in step 1 to be downloaded
  4. save pipeline
  5. delete secure file and reupload

Logs

Fix

#591

Tasks

@vmapetr
Copy link
Contributor

vmapetr commented Apr 1, 2024

Hi @aklakina - thanks for reporting!
We are working on more prioritized issues at the moment, but will get back to this one soon.

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

No branches or pull requests

2 participants