Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

When called with params configuration, shouldn't check for any other source #10

Closed
jeffschwartz opened this issue Jul 10, 2018 · 0 comments
Closed

When called with params configuration, shouldn't check for any other source #10

jeffschwartz opened this issue Jul 10, 2018 · 0 comments
Assignees
@jeffschwartz
Labels
bug Something isn't working
Milestone
v0.2.1

Comments

@jeffschwartz
Copy link
Collaborator

jeffschwartz commented Jul 10, 2018 •
edited

Buster fails when reading command line configuration data belonging to the application that launched it with paramsConfig. The solution is to always read paramsConfig first and if supplied to not search any other source for configuration data.
@jeffschwartz jeffschwartz added the bug Something isn't working label Jul 10, 2018
@jeffschwartz jeffschwartz added this to the v0.2.1 milestone Jul 10, 2018
@jeffschwartz jeffschwartz self-assigned this Jul 10, 2018
jeffschwartz added a commit that referenced this issue Jul 10, 2018
@jeffschwartz
When called with params configuration,
a67c8cc 
shouldn't check for any other source
addressed issue #10
jeffschwartz added a commit that referenced this issue Jul 10, 2018
@jeffschwartz
When called with params configuration, shouldn't
133f1b6 
check for any other source - addresses issue #10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jeffschwartz jeffschwartz

Labels
bug Something isn't working
Projects
None yet
Milestone
v0.2.1
Development

No branches or pull requests
1 participant
@jeffschwartz