Skip to content
This repository was archived by the owner on Mar 15, 2021. It is now read-only.

Ignore unknown config fields #120

Open
hexedpackets opened this issue Apr 5, 2019 · 1 comment · Fixed by #147
Open

Ignore unknown config fields #120

hexedpackets opened this issue Apr 5, 2019 · 1 comment · Fixed by #147
Assignees
@hexedpackets
Labels
level:starter type:enhancement

Comments

@hexedpackets
Copy link
Contributor

Right now, unknown config fields will cause a runtime exception. We should ignore these to make it easier to update the config when rolling out new versions.
@hexedpackets hexedpackets mentioned this issue Jul 9, 2019
Merged
@hexedpackets hexedpackets self-assigned this Jul 9, 2019
@hexedpackets
Copy link
Contributor Author

This only works for top-level configuration. Nested config that uses Jackson annotations (such as the output plugins) will still fail on unknown options.

@hexedpackets hexedpackets reopened this Jul 11, 2019
This was referenced Jul 11, 2019
Closed
Merged
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@hexedpackets hexedpackets

Labels
level:starter type:enhancement
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Update configuration to load from yaml or env vars. spotify/ffwd
1 participant
@hexedpackets