@scottfrederick discovered during investigation for for #26147 that our Our own StandardConfigDataLoader suffers from the same issue as #25766 which we fixed for Spring Cloud. We should probably apply Option.PROFILE_SPECIFIC to profile specific imports.