Micronaut Searching Config Using Wrong Application Name In Spring Cloud Config

[DebajitKumarPhukan]

Problem Statement:
Let's say the micronaut.application.name is "MicronautConfigClientExample" and profile/environment is "test", it is actually searching for "micronaut-config-client-example" properties in Spring Config Server. Thus, unable to find the desired configuration. Is it possible to make the kebab format configurable so that developers can turn it off or on as per their own requirement and thus, they would be liable for the degraded performance ?.

Evidence Log:

19:00:41.855 [main] DEBUG i.m.d.s.c.SpringCloudConfigurationClient - Application Name: micronaut-config-client-example, Application Profiles: test, label: null