Micronaut beans do not receive configuration from environments block #12082
Labels
Comments
puneetbehl
added a commit
that referenced
this issue
Dec 6, 2022
Implemented a new MicronautYamlPropertySourceLoader which reads environment specific properties from application.yml file based on the current configured environment. Fixes #12082
puneetbehl
added a commit
that referenced
this issue
Dec 7, 2022
* Support Environments Concept in Micronaut Context Implemented a new MicronautYamlPropertySourceLoader which reads environment specific properties from application.yml file based on the current configured environment. Fixes #12082 * Update GroovyConfigPropertySourceLoaderSpec.groovy
github-project-automation
bot
moved this from In Progress
to Done
in Grails® framework 6.0
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When using Micronaut beans within a Grails 4 / 5 application, the Micronaut beans do not receive configuration information that was provided within the
environmentsblock.Example application: https://github.com/JasonTypesCodes/g5-mn-config
The
my.messageproperty is defined both in the base configuration as well as withinenvironments.developmentIf you start the application locally with the default development environment and then retrieve
http://localhost:8080/helloyou will see:If it is intended that Micronaut beans and other Grails beans will not act the same way in this regard, it should be documented. I believe it would be best to enhance the Micronaut integration so that the same configuration properties are available to both kinds of beans so that we can more easily use Micronaut configurations within Grails applications.
The text was updated successfully, but these errors were encountered: