docs: Enhance documentation for providers.jdbc configuration in provi… #35573
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…der.yaml This commit enhances the documentation for the `providers.jdbc` configuration in the `provider.yaml` file. Specifically, it addresses the missing information about the `allow_driver_path_in_extra` configuration. The added documentation includes details such as the configuration key, default value, type, and a description of its purpose.
|
Closed in favor of #35580 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit enhances the documentation for the
providers.jdbcconfiguration in theprovider.yamlfile. Specifically, it addresses the missing information about theallow_driver_path_in_extraconfiguration. The added documentation includes details such as the configuration key, default value, type, and a description of its purpose.This PR has been raised in context of the issue #35499
Closes: #35499