Azure Key Vault - Support for wildcard filter
See original GitHub issueAs of today you have 2 options to filter the secrets:
- Use
*
to get all the secrets - Use
<secret-name>
to get one specific secret
However, it would be nice to be able to use a filter sucht as Api-*
that will get all the secrets that start with Api-
such as Api-DeploymentPassword
Issue Analytics
- State:
- Created 6 years ago
- Reactions:4
- Comments:7 (7 by maintainers)
Top Results From Across the Web
AzureKeyVault@2 - Azure Key Vault v2 task - Microsoft Learn
Download Azure Key Vault secrets. ... Select the service connection for the Azure subscription containing ... SecretsFilter - Secrets filter
Read more >az appconfig kv list --key filter not working for * wildcard
I have a KeyValue pair in azure appConfiguration.
Read more >Best practice of using Secrets in Azure DevOps - Saman Ahmadi
Linking an Azure KeyVault to Azure DevOps Variable Group ... The first is to filter secrets using the '*' wildcard or the secret's...
Read more >Azure – Data Factory – changing Source path of a file from ...
All files are the same so this should be OK. Next I go to the Pipeline and set up the Wildcard in here...
Read more >Free Automated SSL Certificates in Azure KeyVault ... - YouTube
Azure KeyVault ACME Bot is a solution provided by Tatsuro Shibamura to manage and automate SSL certificates in Azure KeyVault.
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 Free
Top 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
Hi Tom, We discussed this internally and azure key-vault does not have an API for supporting wild cards in secrets lookup and hence we have not done it.
@tomkerkhove - . This has risk of perf degradation without appropriate API support from Azure. We are not planning to pick this up anytime soon. I’m closing this as a suggestion.