chore: extend FS config loader to allow yaml configs #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
jsteenb2
force-pushed
the
chore/allow_yaml_config_loading
branch
from
b5c4bfe
to
b72f1a5
Compare
johns31459
approved these changes
Jan 31, 2024
jsteenb2
force-pushed
the
chore/allow_yaml_config_loading
branch
from
b72f1a5
to
b773493
Compare
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.
one bit of issue we have with running funcs locally, is the ability to write a yaml config, which is accepted by the faas backend, but locally it does not support it. This is a small change to load the config and if its yaml convert it to a normalized json value as expected by the Run func.