Incorrect "Value is not accepted" in AzureKeyVault task
See original GitHub issueI’m setting runAsPreJob
to false
and secretsFilter
to a quoted comma-delimited string and I get:
Value is not accepted: Valid values: “EditableOptions”.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Common error codes for Azure Key Vault | Microsoft Learn
VaultAlreadyExists, Your attempt to create a new key vault with the specified name has failed since the name is already in use. If...
Read more >AzureKeyVault task not accepting variable as keyvaultname
This format you're trying to use: KeyVaultName: $($env:KVNAME). That's for accessing variables within a powershell script.
Read more >Azure Key Vault Task version 1.0.21 - Visual Studio Feedback
Error: Could not fetch access token for Azure. Status code: 400, status message: Bad Request. 2018-08-17T19:44:59.5539829Z ##[debug]Processed: ##vso[task ...
Read more >Using secrets from Azure Key Vault in a pipeline
Provide any value that will be accepted as a password for a MySQL database. Task 3: Check the Azure Pipeline. Now, lets go...
Read more >Using Azure Key Vault Secrets from your DevOps pipelines
My Azure Key Vault already contains my required secrets. Ensure that this gets done before continuing to make the following steps easier. When ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The PR with the fix was completed, the related changes for the AzureKeyVault task will be shipped with the 200th sprint release of Azure DevOps. We will update the ticket once these changes will be fully rollout to all Azure DevOps users.
This is now released in version 1.202.0 of the extension.