feat: allow cli args to be set via env vars#88
Merged
MacroPower merged 1 commit intomainfrom Aug 3, 2025
Merged
Conversation
e5147fa to
14f7730
Compare
14f7730 to
fd61b80
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Closes #83
This pull request introduces functionality to bind environment variables to any command-line flags in the CLI.
Environment variables are named using the
KAT_<FLAG_NAME>convention, where flag names are converted to uppercase and dashes are replaced with underscores. We also update flag usage descriptions to include the corresponding environment variable names.Order of precedence: arguments > environment variables > config file > default values
I considered using viper here but didn't like that it'd be adding a pretty large library with multiple dependencies just for this.