Initial implementation of a runtime configuration mechanism #14
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
…easier config modification.
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.
The goal here is to allow easier config modification. Currently the resource configuration is defined in code. However it doesn't allow for more dynamic runtime configuration settings that may be needed. For instance, if we need to rerun a specific task, we could set in the runtime configuration .toml file a "ignore cache" flag.
Similarly, if multiple people are running locally, instead of overwriting each other's base config, we can have a personal runtime config (that we don't commit to the repo - please excuse the example...) to let us e.g. define the location of files on our personal computers.