oscerd commented on PR #1927: URL: https://github.com/apache/camel-spring-boot/pull/1927#issuecomment-5566984446
Is `management.server.address` now defaulted to loopback for the other components as well, or only here? As far as I can see this starter is the only thing in the repo that opens a separate management listener, so there would be nothing to default elsewhere: `management.server.port` and `management.server.address` are set only in `ObservabilityServicesEnvironmentPostProcessor`, the other two `EnvironmentPostProcessor` implementations (`CamelCloudConfigEnvironmentPostProcessor`, `CamelVirtualThreadEnvironmentPostProcessor`) touch no management properties, and nothing references `management.port` or `ManagementServerProperties`. The other `management.server.*` hits are `management.server.accesslog.*`, which is our own access-log config rather than the bind address. Spring Boot's own default is no separate management port at all, with actuator served on the main application port that the app already binds deliberately, and `management.server.address` only takes effect once a separate port is configured. So unless I have missed a starter that opens one, this is the only place that needed it. Worth confirming though, since if another starter does grow a management listener later it will inherit the all-interfaces default again. _Comment by Claude Code on behalf of Andrea Cosentino._ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
