Unlike many places, @Refreshable and @ConfigurationProperties strictly require kebab-case for proper function

[sdedic]

Expected Behavior

Rather a documentation suggestion, than a code bug.

Documentation says that property bindings should be declared in kebab-case, but injecting camelCase names works as well (compatibility mode ?), using regular @Value or @ConfigurationProperties - just for initial load only. This is not the case for @Refreshable and automated refresh of @ConfigurationProperties beans.

Actual Behaviour

If @Refreshable("camelCase") is used, the annotated object is NOT refreshed on camel-case or camelCase property change; similarly if @ConfigurationProperties("camelCase") is used, then the bean IS initially loaded, but subsequent refresh event for camel-case property does not re-load that configuration bean's values.

The documentation could warn to strictly adhere to kebab-case here. It's hard to spot since it is an exception from otherwise relexad behaviour in other places, so it could be at least documented.

Steps To Reproduce

1. Declare a @ConfigurationProperties(:"camelCase") with e.g. String name member
2. Observe that the "name" member actually loaded from the configuration property
3. Change the application.properties', property camel-case.name
4. Have a Environment.refreshAndDiff and appropriate Refresh event fired.
5. Observe the bean's property did NOT reload

Environment Information

• Ubuntu Linux 22.04
• Micronaut 4.7.6

Example Application

No response

Version

4.7.6