JOC Audit log api name ./job_chain_nodes/activate does not correspond to operation "skip"

Current Situation

• When the user perform some intervention in the JOC Cockpit, a audit log entry is added to the JOC audit log with API being called and parameters.
• In the JOC Audit Log
  • for the job operation stop the API ./jobs/stop is called, similarly for the operation unstop,
  • for the job node operation skip the API ./job_chain_nodes/skip is called
  • but for the job node operation unskip the API ./job_chain_nodes/activate is called - which does not correspond to the name of the operation.

• 2018-09-27 09:58:47,935 INFO  REQUEST: ./job_chain_nodes/skip - USER: root - PARAMS: {"jobChain":"/ParallelExec/job_chain1","node":"splitL1:230","jobschedulerId":"jobscheduler12_4412"} - COMMENT: Ticket#2018092510000055 - TIMESPENT: - - TICKET: -
  2018-09-27 09:58:59,325 INFO  REQUEST: ./job_chain_nodes/activate - USER: root - PARAMS: {"jobChain":"/ParallelExec/job_chain1","node":"splitL1:230","jobschedulerId":"jobscheduler12_4412"} - COMMENT: Ticket#2018092510000055 - TIMESPENT: - - TICKET: -
  2018-09-27 09:59:10,111 INFO  REQUEST: ./jobs/stop - USER: root - PARAMS: {"job":"/ParallelExec/splitL2","jobschedulerId":"jobscheduler12_4412"} - COMMENT: Ticket#2018092510000055 - TIMESPENT: - - TICKET: -
  2018-09-27 09:59:21,306 INFO  REQUEST: ./jobs/unstop - USER: root - PARAMS: {"job":"/ParallelExec/splitL2","jobschedulerId":"jobscheduler12_4412"} - COMMENT: Ticket#2018092510000055 - TIMESPENT: - - TICKET: -
  

Desired Situation

• The API names should be consistent with the operations

Maintainer Notes

• API methods names generally do not reflect the same wording that the JOC Cockpit offers to users. The method names have been chosen to reflect the API behavior.
• The observation in the audit log that operation names differ from API names is valid for all users who use JOC Cockpit in other languages than English. We therefore intend to add a new feature JOC-557 that adds explicit operation names to the audit log.