Spring Boot generates a metadata file that we use to avoid loading an auto-configuration class when a basic condition doesn't match.
ManagementContextConfigurationImportSelector is using a similar mechanism but does not filter early such candidates. It would be nice if it did it for consistency.
Concretely, it means that the annotation processor should be upgraded to process @ManagementContextConfiguration (currently it doesn't) and the filtering mechanism should be shared ideally.
Comment From: snicoll
Doing this would complement the support that was improved in 2.3.x for sub-imports, see #12157