Skip to content

Conversation

@jerryleooo
Copy link
Member

Description

Is this change a fix, improvement, new feature, refactoring, or other?

This is an improvement on docs.

Is this a change to the core query engine, a connector, client library, or the SPI interfaces? (be specific)

No, only adding docs

How would you describe this change to a non-technical end user or system administrator?

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:

# Section
* Adding docs for JDBC connector extra credentials ({issue}`1910`)

@cla-bot cla-bot bot added the cla-signed label Apr 5, 2022
@jerryleooo jerryleooo requested review from ebyhr, jhlodin and mosabua and removed request for ebyhr and mosabua April 5, 2022 08:26
@github-actions github-actions bot added the docs label Apr 5, 2022
@ebyhr ebyhr requested review from hashhar and removed request for ebyhr April 5, 2022 09:35
Copy link
Member

@mosabua mosabua left a 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.

#11187

@jerryleooo jerryleooo force-pushed the extra_credentials_docs branch from b05178e to c0191a2 Compare April 7, 2022 02:56
@jerryleooo
Copy link
Member Author

@mosabua thanks for the review, I have made changes accordingly

@jerryleooo jerryleooo requested a review from mosabua April 11, 2022 02:25
Copy link
Member

@mosabua mosabua left a 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

@mosabua mosabua removed the request for review from jhlodin April 11, 2022 22:57
@hashhar hashhar removed their request for review April 25, 2022 08:14
@bitsondatadev
Copy link
Member

👋 @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.

@hashhar
Copy link
Member

hashhar commented Nov 19, 2022

This is addressed by #14454.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

Document use of extra credentials in JDBC connectors

4 participants