Add the ability to trigger a Quartz job on-demand through an Actuator endpoint

[nosan]

Before this commit, triggering a Quartz job on demand was not possible. This commit introduces a new @WriteOperation endpoint at /actuator/quartz/jobs/{groupName}/{jobName}/trigger, allowing a job to be triggered by specifying the {jobName}, {groupName}, and an optional JobDataMap.

See gh-42530

$ curl 'http://localhost:8080/actuator/quartz/jobs/samples/jobOne/trigger' -i -X POST \
    -H 'Content-Type: application/json' \
    -d '{"jobData":{"key":"value","keyN":"valueN"}}'
    

HTTP/1.1 200 OK
Content-Type: application/vnd.spring-boot.actuator.v3+json
Content-Length: 166

{
  "group" : "samples",
  "name" : "jobOne",
  "className" : "org.springframework.scheduling.quartz.DelegatingJob",
  "triggerTime" : "2024-11-10T09:44:05.425233Z"
}

[snicoll]

Can you explain why you had to change this?

[nosan]

I added a comment regarding these changes in the #42530 (comment)

The Map<String, String> request body does not support complex values like Map or List, only basic JSON types.

For example, this JSON is not supported at the moment:

{
  "jobData": {
    "key": "value"
  }
}

WebMvc:

[org.springframework.http.converter.HttpMessageNotReadableException: 
JSON parse error: Cannot deserialize value of type `java.lang.String` from Object value (token `JsonToken.START_OBJECT`)]

WebFlux:

org.springframework.core.codec.DecodingException: JSON decoding error: Cannot deserialize value of type `java.lang.String` from Object value (token `JsonToken.START_OBJECT`)

[snicoll]

Unfortunately, we don't intend to support arbitrary input this way. This part is covered in the reference guide.

Can you please revert to allow jobs to be invoked on demand without custom data?

In the comment you've referenced you stated that "By the way, Jersey works fine". I am not sure what you mean by that but if there is something that needs to be done for things to work currently the same way on all stacks, please create a separate issue with more details.

[nosan]

I meant that @WebEndpointTest with JERSEY infrastructure does support Map<String, Object as an endpoint parameter.

If I revert my changes related to @RequestBody Map<String, Object the MVC and WebFlux will fail but Jersey will not.

You can reproduce this issue by running this test QuartzEndpointWebIntegrationTests.quartzTriggerJobWithCustomData

Branch: https://github.com/nosan/spring-boot/tree/42530-map-issue

[snicoll]

Thanks @nosan, I've created #43209 and reproduced the problem.

[nosan]

Thanks, @snicoll
PR has been updated.