Prior to this commit, the native image support for scanning Flyway
migration scripts would not scan sub-folders at runtime when running a
Native image.
This commit ensures that the resource scanning at runtime also considers
sub-directories for native images.
Fixes gh-49661
This commit updates the GraphQL slice tests to also consider
`@ControllerAdvice`-annotated beans, since Spring GraphQL loads
`@GraphQlExceptionHandler`s declared in `@ControllerAdvice` beans.
This also aligns `@GraphQlTest` with `@WebMvcTest`.
See gh-49660
Signed-off-by: Louis Morgan <ljrmorgan@gmail.com>
Prior to this commit, the `EndpointRequest` request matcher generator
would create many, complex matchers for the case of health groups
exposed on additional paths.
This commit revisits the matcher generation and simplifies their
matching to avoid conflicts with other matchers.
Fixes gh-49648
Prior to this commit, the Servlet and Reactive CloudFoundry Actuator
Handler mapping would only handle requests to actual Actuator endpoints.
Here, our original intent has always been to reserve this URL namespace
for the CloudFoundry use case and not delegate to other handler
mappings.
This commit ensures that requests under this path should be processed by
known endpoints, or result in a "HTTP 403 Forbidden" response.
Fixes gh-49645
When management.endpoints.web.base-path is empty and management runs
on a different port, EndpointRequest.toLinks() and toAnyEndpoint()
do not match the links endpoint consistently.
Derive the links path based on the management port type on both
servlet and reactive sides, and add regression tests for each
implementation.
See gh-49591
Signed-off-by: bbbbooo <hyeons1213@gmail.com>
Prior to this commit, choosing a "websocket" transport for your RSocket
endpoint with `spring.rsocket.server.port` would not only expose the
endpoint on that specific port, but also on the main server.
This commit refines the auto-configuration condition to only add a route
on the main server if the separate port is not chosen.
Fixes gh-49592
Prior to this commit, applying the "spring.main.cloud-platform=none"
property would apply this choice to the relevant auto-configuration
conditions, but the `CloudPlatform` enum itself would still signal that
cloud features like header forwarding is enabled.
This commit ensures that "NONE" disables such features.
Fixes gh-49478
Update `ConfigDataEnvironment` so `spring.config.import`
properties defined in environment or system properties
are ordered correctly.
See gh-49324
Signed-off-by: qnnn <qiunan@cmbchina.com>