The Tasks API in the current version of Nexus provides the ability to view, execute, and stop existing tasks that were created in the repository admin user interface. There is a desire to interact more extensively with scheduling tasks through the API, namely, to be able to perform all CRUD operations.
For scheduling tasks outside of the admin user interface, you can of course get by with a Groovy script that is passed and executed through the Nexus Script API. But the Groovy scripting solution is one of the reasons for the security breach.
Please clarify whether there will be an opportunity for a more simplified and safer work when automating task scheduling, for example, expanding the API Tasks functionality. Or if something like that already exists, please direct it to the right decision.