Skip to content
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

access to vault to have better error message #14

Closed
dzmitry-lahoda opened this issue Oct 10, 2020 · 3 comments
Closed

access to vault to have better error message #14

dzmitry-lahoda opened this issue Oct 10, 2020 · 3 comments
Labels
feature-request This issue requires a new behavior in the product in order be resolved. KeyVault Key Vault

Comments

@dzmitry-lahoda
Copy link

try next with wrong az account:

    let mut key_vault_client = KeyVaultClient::new(&creds, "lahodapro");
    println!("list secrets for");
    let secrets = key_vault_client.list_secrets().await?;

Expected: error message about wrong auth usage
Actual: error about some value is missing
Notes: that is very important that entry point to azure via auth to have guiding errors, not cryptic

@rylev rylev added the feature-request This issue requires a new behavior in the product in order be resolved. label Oct 12, 2020
@guywaldman
Copy link
Contributor

guywaldman commented Oct 14, 2020

Thanks, agree. I kept it very simple and a lot of the errors can be improved now that it's part of the official repo.

Speaking of, noticed that the error message here is not accurate, should accommodate endpoints in other clouds.

@ftt
Copy link

ftt commented Feb 19, 2022

I think this should be covered by [Proposal] Error Handling #625.

@rylev
Copy link
Contributor

rylev commented Feb 21, 2022

Just as an FYI: #625 won't solve this but it does provide facilities for improving the error message.

@cataggar cataggar closed this as not planned Won't fix, can't repro, duplicate, stale Oct 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request This issue requires a new behavior in the product in order be resolved. KeyVault Key Vault
Projects
None yet
Development

No branches or pull requests

5 participants