Skip to content
This repository has been archived by the owner on Feb 7, 2020. It is now read-only.

Add support for setting configs #30

Merged
merged 4 commits into from
May 3, 2019
Merged

Add support for setting configs #30

merged 4 commits into from
May 3, 2019

Conversation

bucko13
Copy link
Contributor

@bucko13 bucko13 commented May 3, 2019

This implements bcfg for handling config parsing adding the ability to set configs by passing in an options object, using a config file, env vars prefaced with CHAINPOINT_ or passing via argv in command line.

This PR also uses this new interface for passing two values that are available as constants in the code base and instead uses those constants as a fallback.

@bucko13
Copy link
Contributor Author

bucko13 commented May 3, 2019

@jacohend @jasonbukowski - Pretty simple update but might be useful for broadening ways to pass configs in other modules as per some discussion offline with @jacohend. Tests should hopefully give an idea of how to set and get configs with bcfg.

…th Promise.all and enabling timeouts for fetch in browser
@bucko13
Copy link
Contributor Author

bucko13 commented May 3, 2019

Going to merge these in. Let me know if there are any questions about the config tooling!

@bucko13 bucko13 merged commit 919d68b into core-v2-support May 3, 2019
@bucko13 bucko13 deleted the configs branch May 3, 2019 21:38
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant