-
Notifications
You must be signed in to change notification settings - Fork 3.4k
add docs for jdbc extra credentials, fixing #1910 #11791
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
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.
We should not add the CLI and JDBC related docs into the connector docs .. instead we should document the extra credential usage in the CLI page and the JDBC driver page and then link there.
There is an ongoing PR that needs to be merged asap so that you can proceed with this as a next step.
b05178e to
c0191a2
Compare
|
@mosabua thanks for the review, I have made changes accordingly |
mosabua
left a comment
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.
A couple of general things to update please
- leave secret usage to be the first solution mentioned
- wrap extra credential fragment text at 80 char
- explain what you mean by "key" in those context, and where the credentials are looked up from, maybe this whole thing is worth a separate page we link to in the authentication docs, from the current explanation I do not know how to use this
- provide separate section in CLI docs about extra credential usage
- provide separate section in JDBC docs
- link to those sections in the connectors
|
👋 @jerryleooo - this PR is inactive and doesn't seem to be under development, and it might already be implemented. If you'd like to continue work on this at any point in the future, feel free to re-open. |
|
This is addressed by #14454. |
Description
This is an improvement on docs.
No, only adding docs
N/A
Related issues, pull requests, and links
Documentation
( ) No documentation is needed.
(*) Sufficient documentation is included in this PR.
( ) Documentation PR is available with #prnumber.
( ) Documentation issue #issuenumber is filed, and can be handled later.
Release notes
( ) No release notes entries required.
(*) Release notes entries required with the following suggested text: