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

AzureKeyVault@1, @2: Fix incorrect inputs properties #15162

Conversation

winstliu
Copy link
Member

Task name: AzureKeyVault@1, AzureKeyVault@2

Description: The inputs JSON in task.json was using options instead of properties for the SecretsFilter & RunAsPreJob inputs, leading to incorrect validation downstream in the azure-pipelines-vscode extension.

Documentation changes required: (Y/N) N

Added unit tests: (Y/N) N

Attached related issue: (Y/N) Fixes microsoft/azure-pipelines-vscode#410.

Checklist:

  • Task version was bumped - please check instruction how to do it
  • Checked that applied changes work as expected

This is input validation, so I'm unsure how to test it as I don't know how the schema gets generated.

@winstliu
Copy link
Member Author

winstliu commented Jan 4, 2022

@rohit-batra, @tauhid621 - any chance one of you could review & merge this change? There's been another ask to fix this from users of the VS Code extension.

@KonstantinTyukalov
Copy link
Contributor

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 4 pipeline(s).

@KonstantinTyukalov
Copy link
Contributor

@rohit-batra, @rvairavelu - could you please take a look at this changes?

@KonstantinTyukalov
Copy link
Contributor

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 4 pipeline(s).

@@ -14,7 +14,7 @@
"author": "Microsoft Corporation",
"version": {
"Major": 1,
"Minor": 198,
"Minor": 199,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should be 200 now

@@ -14,7 +14,7 @@
"author": "Microsoft Corporation",
"version": {
"Major": 2,
"Minor": 189,
"Minor": 199,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should be 200 now

@KonstantinTyukalov
Copy link
Contributor

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 4 pipeline(s).

@KonstantinTyukalov
Copy link
Contributor

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 4 pipeline(s).

@winstliu
Copy link
Member Author

Yay, thank you!

@winstliu winstliu deleted the users/winstonliu/fix-incorrect-akv-validation branch January 24, 2022 18:00
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.

Incorrect "Value is not accepted" in AzureKeyVault task
3 participants