Auto-configuration happens at runtime, not as code generation. Therefore, there's really not an XML config file or a
Java class to look at.
However, if you have the Actuator in play at runtime, then the /beans endpoint will produce a JSON document describing all of the beans in the application context as well as what they're injected with. And the /autoconfig endpoint will produce a report explaining the auto-configuration decisions that were made (grouped by conditions that passed and conditions that failed).