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.

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

warn or fail if an application.yaml is provided without the quarkus-config-yaml dependency #13227

Closed
vsevel opened this issue Nov 11, 2020 · 3 comments · Fixed by #35298
Closed

Comments

@vsevel
Copy link
Contributor

vsevel commented Nov 11, 2020

Description
If configuration is provided through a yaml file, but the quarkus-config-yaml has not been added, the configuration module will silently ignore the yaml file. it may take some time for the user to figure out that is what is happening, incorrectly thinking there is a bug in quarkus or smallrye config.
The proposition is to fail quarkus startup, or at least WARN the user that no properties file has been found, and a yaml file has been found,but will be ignored.

see also this discussion in the forum.

@vsevel vsevel added the kind/enhancement New feature or request label Nov 11, 2020
@ghost ghost added the area/smallrye label Nov 11, 2020
@ghost
Copy link

ghost commented Nov 11, 2020

@radcortez
Copy link
Member

I'm wondering if we should just add the YAML source to the list of the default sources.

@vsevel
Copy link
Contributor Author

vsevel commented Dec 4, 2020

@radcortez as yaml configuration looks more and more the standard nowdays, I completely agree.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants