Project: springxd
Issue XD-742: REST API for Job Management
Spring Batch Admin provides a complete, but outdated implementation style, which covers the full administrative lifecycle of batch jobs, their creation, stop/start, and retrieving information about previous job executions and the status of currently executing job executions. SpringXD has a different way of deploying, starting, and stopping jobs - by sending messages to containers that run the batch job. However, the reporting state of a job is still stored in a common job repository. The purpose of this story is to take the first step to merging in the existing code base that focuses only on the retrieval of information from Spring Batch Admin’s Job controller. The current ‘REST API’ style of these commands should stay as close to the original spring batch admin style as possible. There are several reasons for this 1. It works, and time to springone is short, and we mgmt has expectations around deliverables that we must strive to meet. 2. It gives Andrew a working contract to start developing a UI 3. We can take on this technical debt, but refactor after RC1 and before GA while and deliver end-user functionality. Attached is the list of endpoints in spring batch admin
Story points: 20