TimeConverterRegistrar silenly ignores incovertible config properties on injection

[sdedic]

Expected Behavior

A message like the following should appear in the log/exception messages:

Unable to convert value [60 seconds] to target type [Duration] due to: Unparseable date format (60 seconds). Should either be a ISO-8601 duration or a round number followed by the unit type

which is informative & points out the root cause.

Actual Behaviour

The following message/exception apears:

Error resolving property value [${health-check-cache-expiration}]. Property doesn't exist 

The TimeConverterRegistrar rejects other malformed specifications, like 60us with an appropriate message, but completely misformatted values are silently ignored and misreported as missing. Other malformed inputs, like integers in i.e. micronaut.server.port report a conversion error / invalid property format.

I believe the reason is that when TimeConverterRegistrar rejects the text with the initial regexp check, it does not call context.reject() unlike the other validations.

TimeConverterRegistrar also accepts some malformed inputs without any errors:

• 60hs - interprets as 60 hours
• 60ds - interprets as 60 days

Steps To Reproduce

1. Have a configuraton bean with

@Value("${health-check-cache-expiration}")
private Duration healthCheckCacheExpiration;

2. Have an application with

healthCheckCacheExpiration: 60 seconds

(converting a service from a dropwizard-based implementation, so different conversion formats were used, and remained in the config)

3. attempt to inject (otherwise materialize) the configuration bean, so the value is injected and converted from the configuration.

Environment Information

• Ubuntu Linux 22.04
• OpenJDK Runtime Environment (build 21+35-2513)

Example Application

No response

Version

4.6.5