Extending and customizing auto-configuration classes provided by Spring Boot
How to dynamically exclude selected Spring Boot auto-configuration classes using profile groups
Problem statement Imagine a scenario when we need to enable certain spring boot auto-configuration on a subset of environments only. The reason for that may be that i.e. our new feature will use new database (mongo) which hasn’t been setup on all environments yet for some reason, but we don’t want this issue to stop us from deploying new version of the application.
Not all spring boot auto-configurations support disabling them using property.