Copy job
Compliance Engines limit any syncing operations while a profiling or masking job is running. When using DCT job move, execute, or migrate operations, please ensure that the target Compliance Engine is in an idle state. Future Compliance enhancements to DCT will remove this limitation.
The Masking Job Copy operation creates a duplicate of a job with a separate reference for that new copy. This operation supports SDLC workflows as DCT will maintain unique references for each instance of a masking job, enabling them to be managed independently.
User interface documentation
Job copy can be run via the DCT UI by accessing a compliance job's detailed view and selecting the ellipsis in the top right corner and clicking on "copy". This will open a window to select the target engine, the new name of the transferred job, source and target environment details, and relevant tags.
API documentation
For input, the user must specify the target engine along with the environment on the target engine that the job will be copied onto. The engine and environment pair is what uniquely identifies a copy of the Masking Job. Calling the COPY API against the same target engine and environment effectively serves as a re-sync and does not create a new DCT MaskingJob entity.
Example of copying a MaskingJob to engine with ID 2 and environment named ‘prod-env’:
curl -X 'POST' \
'https://<APPLIANCE_ADDRESS>/v3/masking-jobs/d53812ce-9186-485d-a388-44bc52087ead/copy' \
-H 'accept: application/json' \
-H 'Authorization: <API_KEY>' \
-H 'Content-Type: application/json' \
-d '{
"target_engine_id": "2",
"target_environment_id": "prod-env"
}'
MaskingJob sync will not copy connector credentials to another engine. In order to make a copied job executable outside of DCT, the credentials must be set on the Connector itself. The connectors for a MaskingJob can be searched for, updated, and tested directly via DCT.
Example of listing connectors for a MaskingJob:
curl -X 'GET' \
'https://<APPLIANCE_ADDRESS>/v3/masking-jobs/d53812ce-9186-485d-a388-44bc52087ead/connectors' \
-H 'accept: application/json' \
-H 'Authorization: <API_KEY>'
Example of updating a connector’s credentials:
curl -X 'PATCH' \
'<https://<APPLIANCE_ADDRESS>/v3/connectors/2-DATABASE-23'> \
-H 'accept: application/json' \
-H 'Authorization: <API_KEY>' \
-H 'Content-Type: application/json' \
-d '{
"username": "USER123",
"password": "password123"
}'
Example of testing a connector:
curl -X 'POST' \
'<https://<APPLIANCE_ADDRESS>/v3/connectors/2-DATABASE-23/test'> \
-H 'accept: application/json' \
-H 'Authorization: <API_KEY>' \