Found auto-configuration class problems:
- org.springframework.boot.actuate.autoconfigure.amqp.RabbitHealthContributorAutoConfiguration:
- after 'org.springframework.boot.amqp.autoconfigure.RabbitAutoConfiguration' is from an optional dependency and should be declared in afterName
- org.springframework.boot.actuate.autoconfigure.metrics.amqp.RabbitMetricsAutoConfiguration:
- after 'org.springframework.boot.amqp.autoconfigure.RabbitAutoConfiguration' is from an optional dependency and should be declared in afterName
Binding in the child context does not work correctly when an
environment prefix has been configured. The prefix is not applied
to the child context's Environment and, therefore, prefixed
environment variables are ignored during binding.
We can fix the problem by reusing the parent context's
ManagementServerProperties rather than binding them again in the
child context. Doing so will fix the problem reported in gh-45857
that was introduced in 020fd7b and will also avoid an unnecessary
second binding of the properties.
gh-45858 may fix the problem more generally by applying the prefix
to the child context's environment. This would benefit situations
where the properties need to be bound in the child context because
they haven't already been bound in the parent.
Closes gh-45847
Support for Zipkin export using a RestTemplate- or WebClient-based
sender was deprecated in 3.3 and then removed in 3.5. This made
redundant the tests that checked there was no cycle when using
RestTemplate or WebClient.
Closes gh-45847
Update `CloudFoundryActuatorAutoConfiguration` so that CSRF protection
is ignored for Cloud Foundry endpoint requests. This aligns with the
behavior of Spring Boot 3.4 where `ignoring()` was used for security
configuration. With the migration to `permitAll()` we now need
additional CSRF configuration.
Fixes gh-45848
