Log warning if a known configuration file exists and we have no parser #1853
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.
Signed-off-by: Tomas Langer tomas.langer@oracle.com
Currently if you have for example
application.yaml
on classpath, yet forget to addhelidon-config-yaml
module, the file is ignored byConfig
.This change at least logs a warning when no configuration or meta-configuration file is found, and:
application.*
and/ormeta-config.*
in current directoryapplication.*
and/ormeta-config.*
on classpathexists and there is no parser configured for it, for the following file suffixes:
yaml
conf
json