Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Conversation

aklakina
Copy link

@aklakina aklakina commented Mar 26, 2024

This pull request is supposed to fix the following issue: microsoft/azure-pipelines-tasks#6885

In the classic pipelines the secure file reference was stored by the GUID of the secure file which was generated upon upload. The flaw in this design was that the secure file has no option to update it's content.

When for example a config file has to be changed because of infrastructural changes then every classic pipeline using that secure file breaks because the newly uploaded secure file has a different GUID.

In the context of yaml pipelines this does not cause any issue because we store the secure file by name.

@aklakina
Copy link
Author

This pull request is strongly related to the following one: microsoft/azure-devops-node-api#591

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

Successfully merging this pull request may close these issues.

1 participant

Morty Proxy This is a proxified and sanitized view of the page, visit original site.