Skip to content

Conversation

reynoldsliu
Copy link

Previously, ConditionsReportEndpoint only traversed the parent ApplicationContext hierarchy, which caused conditions from child contexts (e.g. the Actuator's management context) to be missing from the report.

This commit updates the context collection logic to:

  • Traverse both parent and child ApplicationContexts
  • Use seenIds to avoid duplicate or cyclic references
  • Ensure child contexts (like Actuator context) are now included in the conditions evaluation report

Closes gh-6698

Previously, ConditionsReportEndpoint only traversed the parent
ApplicationContext hierarchy, which caused conditions from
child contexts (e.g. the Actuator's management context) to be
missing from the report.

This commit updates the context collection logic to:
- Traverse both parent and child ApplicationContexts
- Use seenIds to avoid duplicate or cyclic references
- Ensure child contexts (like Actuator context) are now
  included in the conditions evaluation report

Closes spring-projectsgh-6698

Signed-off-by: Reynolds Liu <reynoldsliu@users.noreply.github.com>
@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Aug 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: waiting-for-triage An issue we've not yet triaged
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Logged auto-configuration report doesn't include conditions evaluated in child contexts
2 participants