-
Notifications
You must be signed in to change notification settings - Fork 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
feat(ingest): Support config variable for specifying a direct privat… #6609
feat(ingest): Support config variable for specifying a direct privat… #6609
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
one nit but LGTM other than that
raise ValueError( | ||
f"'private_key_path' was none " | ||
f"but should be set when using {v} authentication" | ||
f"Both `private_key` and `private_key_path` are none. " |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: i see that we're throwing the error below, but ideally we should just be doing the error checking in one place
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes. This is the main place I intend to keep error checking at. The assertion in below method was added primarily for linter.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To remove the assert, we can add if.. elif..
, however assert seemed cleaner to me.
…e key
Checklist