-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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.
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
Add more tests around config parsing changes from common config PR #4433
Conversation
@trevorwhitney can we name this PR a little more descriptively please? We use the PR names for our changelogs |
@dannykopping yes, absolutely, sorry I didn't mean to actually name it after that terrible commit! |
Haha no sweat! Thanks 🙌 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍
bdc07d1
to
f4a68c4
Compare
Going to wait on resolving conflicts until #4400 is merged as this builds on that branch |
Signed-off-by: Trevor Whitney <[email protected]>
Signed-off-by: Trevor Whitney <[email protected]>
Signed-off-by: Trevor Whitney <[email protected]>
…here Signed-off-by: Trevor Whitney <[email protected]>
Signed-off-by: Trevor Whitney <[email protected]>
eed3ee7
to
0078ec6
Compare
Signed-off-by: Trevor Whitney <[email protected]>
@dannykopping this should be good to go now, would you mind merging if you have permission to do so? |
You got it 👌 |
What this PR does / why we need it:
Adds a bit more testing around the new config unmarshalling methods to confirm #4419 was not a real bug. It turned out just to be a strange behavior when passing a completely empty yaml file as the config file, like:
This was being used for tests, but is unlikely a case we need to solve for in real usage.
Which issue(s) this PR fixes:
Fixes #4419
Checklist