Add configurable path for script-exporter config file #162
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
|
@ricoberger please consider this pull request |
|
Hi @Monkman08, thanks for your contribution 🙂 |
ricoberger
approved these changes
Nov 10, 2024
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.
Description
This pull request adds the configFile parameter to the values.yaml file in the Helm chart. This parameter allows users to override the script_exporter configuration file argument.
Motivation
Adding the configFile parameter is useful for scenarios where the configuration file is mounted from an external source. This provides greater flexibility in managing the script_exporter configuration.
Changes
Added configFile parameter to values.yaml to override the script_exporter configuration file argument.