-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[Azure] Unable to check if key vault secret exists using environment variables #903
Comments
@victornoventa Operations on Azure Keyvault are 2 groups, first group "Management plan "that creates, update or detele the vault and set the permissions on it. the second group "Data plan" that add, updates, retrieve, or deletes the values stored within the vault To run any operation on the data within azure keyvault you need to use a data plan Authorizer, while the remaining resources operations are using the management plan authorizer. With that said, I think we should expand the newKeyVaultAuth terratest/modules/azure/keyvault.go Line 126 in d1ce8be
terratest/modules/azure/authorizer.go Line 24 in d1ce8be
For more details please check this |
@victornoventa a fix was merged to address this issue. |
I have had issues while running my tests that rely on
modules/azure/keyvault
to check if a secret exists. I have everything set as the instructions tell me to do and everything goes fine with my service principal information set as environment variables. But I can't check if a secret exists because it relies on Az CLI instead. Is there any specific reason for having this relying onNewAuthorizerFromCLI
terratest/modules/azure/keyvault.go
Line 127 in d1ce8be
Instead of relying on
NewAuthorizerFromEnvironment
?https://github.com/Azure/azure-sdk-for-go/blob/master/services/keyvault/auth/auth.go#L19
I mean, I've seen other places using this Authorizer instead:
terratest/modules/azure/authorizer.go
Line 24 in d1ce8be
The text was updated successfully, but these errors were encountered: