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

[FR] Non-technical error reporting for service account errors #66

Open
Greenford opened this issue May 31, 2022 · 0 comments
Open

[FR] Non-technical error reporting for service account errors #66

Greenford opened this issue May 31, 2022 · 0 comments
Labels
enhancement New feature or request fr Feature Request

Comments

@Greenford
Copy link
Collaborator

Should we do some error handling for common service-account related errors? For instance, if the service key is expired then initializing a core class with creds_path would throw:

RefreshError: ('invalid_grant: Invalid JWT Signature.', {'error': 'invalid_grant', 'error_description': 'Invalid JWT Signature.'})

but instead we could try/catch and throw a plain-language error like "Your service account key has expired. Please make a new one and try again".

This would hopefully keep non-technical user working in a notebook from getting blocked and needing a programmer's help.

Another error case might be when the service account key and agent id are for different projects.

@Greenford Greenford added enhancement New feature or request fr Feature Request labels May 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request fr Feature Request
Projects
None yet
Development

No branches or pull requests

1 participant