Closed binlecode closed 5 years ago
fixed 3.2.x in commit https://github.com/binlecode/grails-appinfo/commit/27331624203891573c03bd5ce1ae1db67d03c09a.
now checking 3.3.x branch to see if same issue exists
3.3.x has different bean loading logic for aws-s3 health indicator, so no such issue. closing this issue.
in 3.2.x sample app, when application.yaml has aws-s3 configuration commented, the application fails to bootstrap by error:
APPLICATION FAILED TO START
Description:
A component required a bean named 's3HealthCheck' that could not be found.
When the key is uncommented with empty values, the app can boot.