-
-
Notifications
You must be signed in to change notification settings - Fork 10
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
2.0-alpha1: 404 when listing empty cubbyhole #193
Comments
Fixed in c14ea4d Vault does not distinguish whether listing empty or nonexistent folder. Therefore, a friendly message "The target path is empty or does not exist." will be printed in stderr instead of blank output. |
Now I am getting: $ fedcloud secret list
An unexpected error occurred: Error: Error when accessing secrets on server. Server response: HTTPError: 403 Client Error: Forbidden for url: https://vault.services.fedcloud.eu:8200/v1/cubbyhole/?list=true Would it be correct to simply print out instead: No lockers found. |
This is another error, authentication error, because the locker token is expired (either number of use or lifetime)
Excellent idea, thank you for suggestion. I would change the message little "No secrets found". If the locker was created, it does exist, but only is empty. Furthermore, the |
Then |
Fixed. 64b66f9 |
Thanks! This works now when FEDCLOUD_LOCKER_TOKEN is set and no lockers have been created. But there are two other scenarios where I think the
fedcloud secret list
An unexpected error occurred: Error: Error when accessing secrets on server. Server response: InvalidPath: None, on list https://vault.services.fedcloud.eu:8200/v1/secrets/users/<EGI-ID>egi.eu
fedcloud secret locker check
Error: Error when accessing secrets on server. Server response: Forbidden: permission denied, on get https://vault.services.fedcloud.eu:8200/v1/auth/token/lookup-self
fedcloud secret list
An unexpected error occurred: Error: Error when accessing secrets on server. Server response: HTTPError: 403 Client Error: Forbidden for url: https://vault.services.fedcloud.eu:8200/v1/cubbyhole/?list=true |
We need to catch exceptions and manage the error messages systematically. So far put it on hold as a request for improvement |
Initial checklist
Affected packages and versions
2.0-alpha1
Link to runnable example
No response
Steps to reproduce
fedcloud secret locker create export FEDCLOUD_LOCKER_TOKEN=hvs.CAESIXXX fedcloud secret list
Expected behavior
Return empty list.
Actual behavior
Affected runtime and version
[email protected]
Affected package manager and version
No response
Affected OS and version
No response
Build and bundle tools
No response
The text was updated successfully, but these errors were encountered: