Execute job

With recent updates, all job executions are now centralized to the source engine. The Execute endpoint has been optimized to support efficient job management directly from the source engine, ensuring any updates or modifications are directly applied to the job on the source engine.

This enables users to directly identify, copy, and run masking jobs without the need to manage multiple job instances across different engines.

Executing a MaskingJob now requires solely the source engine reference. Continuous Compliance will handle all necessary preparations for job execution within the original environment, eliminating the need for syncing operations to other engines.

Example of executing a MaskingJob:

CODE

curl -X 'POST' \
  'https://<APPLIANCE_ADDRESS>/v3/masking-jobs/d53812ce-9186-485d-a388-44bc52087ead/execute' \
  -H 'accept: application/json' \
  -H 'Authorization: <API_KEY>' \
  -H 'Content-Type: application/json' \
  -d '{
  "source_engine_id": "2"
}'

For managing MaskingJob credentials securely, users can update job details including connector credentials through the UPDATE API. This ensures all necessary authentication details are correctly configured within the job settings prior to execution.

Example of updating a MaskingJob with connector credentials:

CODE

curl -X 'PATCH' \
  'https://<APPLIANCE_ADDRESS>/v3/masking-jobs/d53812ce-9186-485d-a388-44bc52087ead' \
  -H 'accept: application/json' \
  -H 'Authorization: <API_KEY>' \
  -H 'Content-Type: application/json' \
  -d '{
  "connector_username": "user123",
  "connector_password": "password123"
}'