-
Notifications
You must be signed in to change notification settings - Fork 272
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
Provider can only lookup 25 key vault items when adding variables to a linked variable group #388
Comments
Hi @booyaa Thanks for your feedback, this is a bug. The default secrets response page size is 25 and ADO provider only get the first page. |
@xuzhang3 ideally it should paginate, but if we can have a small workaround for now, like increasing the pageSize to 100 on the API call would be good. |
ADO doesn't look like they expose an option to map to the The Azure api returns a netxtlink prop containing a |
Any news/ETA on this issue? Until it's fixed is there any way to work around it (beside having var group with less than 25 vars)? |
@lisaplapla Currently, the only workaround is having var group with less than 25. This task has been added to our backlog. |
Hello @xuzhang3 , |
I am also experiencing this issue, follow this and will appreciate to know about a resolution. |
I'd like to clarify that the workaround is not so much limiting the size of variable groups to 25, but the number of secrets in the linked Key Vault. If you have a single Key Vault with 100 secrets, creating 4 different variable groups will still only allow you to access the first 25 secrets. Instead, you'd have to set up 4 different Key Vaults, each with max 25 secrets. Then you can link variable groups to each of the Key Vaults and access all the secrets. |
I submit PR #522 to fix this bug, since KV API does not support filter the secret by name and the pagination size is fixed to 25, current fix will read the top 500 secrets from the KV. |
Released in v0.2.0 |
Hi, Today I've faced the same issue. |
Community Note
Terraform (and Azure DevOps Provider) Version
Affected Resource(s)
azuredevops_variable_group
Terraform Configuration Files
Debug Output
https://gist.github.com/booyaa/9ea7705f43a76e759a0436925145973a
Panic Output
n/a
Expected Behavior
Should create variables in the variable group that correspond to the key vault secrets:
var00 .. var25
Actual Behavior
secrets do exist...
Click to expand az keyvault secret list output
Steps to Reproduce
terraform plan && terraform apply
Important Factoids
References
The text was updated successfully, but these errors were encountered: