-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
az keyvault secret fails with error Session.request() got an unexpected keyword argument 'enable_cae' #38082
Comments
Debug log (tenantId zeroed out)
|
Thank you for your feedback. Tagging and routing to the team member best able to assist. |
Hi @stephan-uhlmann, thank you for opening this issue. Rolling back your versions of each
The error you're seeing is caused by |
Thanks for the quick reply! My Azure CLI version is 2.65.0. I install it as an RPM from my distributions (openSUSE Tumbleweed) repository, together with the Python modules. So it might be a packaging error by the distribution, that they don't use the pinned versions but the newest ones? |
Looks like Azure/azure-cli#30062 will fix the issue? |
Sorry for the delay; I was out of office.
Yes, that change should fortunately fix the keyword argument issue 🙂 I'll mark this as resolved since this was ultimately a CLI bug and they've merged a fix. It looks like openSUSE has a bug tracker -- I didn't see anything that looked relevant when searching for "pinned", but it may be worth opening an issue if you can't find one. The CLI resolved a similar bug in the past by pinning their KV dependencies, and this is the first I've heard of this versioning issue since then. That makes me wonder if the distribution is fine and the conflict came from elsewhere. If it is confirmed to be an error from the distribution though, please feel free to update this issue so that we can take that into account in the future. Thanks again for opening this issue! |
Hi @stephan-uhlmann. Thank you for opening this issue and giving us the opportunity to assist. We believe that this has been addressed. If you feel that further discussion is needed, please add a comment with the text "/unresolve" to remove the "issue-addressed" label and continue the conversation. |
Hi @stephan-uhlmann, since you haven’t asked that we |
Describe the bug
Since the last update of azure-keyvault-secrets the
az keyvault secret
commands fail with the errorTo Reproduce
Steps to reproduce the behavior:
az keyvault secret list --vault-name myvault
az keyvault secret show --vault-name myvault --name mysecret --query value -o tsv
Expected behavior
Command runs successfully.
Screenshots
I'll post a debug log as an additional comment, to keep this descripton readable.
Additional context
Commands
az keyvault list
run successfully.Command
az keyvault certificate list --vault-name myvault
also fails with the same error (azure-keyvault-certificates==4.9.0).Maybe there are more, I can test others as well if needed.
The text was updated successfully, but these errors were encountered: