docs: update examples documentation to use of loading from ENV #350
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.
Description
This PR enhances the Druid Operator's documentation to improve clarity. It addresses the following:
Introduction of Environment Variables in Druid Configuration: A new section in the examples documentation introduces the use of environment variables within
common.runtime.properties
. This provides a mechanism for greater configuration flexibility and security. Users can now manage sensitive information or environment-specific values externally, without directly embedding them in the Druid configuration. This was already being used on Allow possibilities to add env var to erase some config value #35 (comment)Practical Example of Environment Variables: A concrete example showcasing the utilization of environment variables for the metadata store configuration (
druid.metadata.storage.connector.*
) is added. This example guides users on how to implement this new feature effectively.Key changed/added files in this PR
docs/examples.md