Good Morning,
We are automating the data masking portion of our Test Data Management application. Currently we are able to login, generate the authorization token, kick off a masking job with a job and Connector ID, check its status then logout.
The purpose of the connector will stay the same with rulesets, inventory, schema, etc with every masking iteration or execution. Challenge is the hostname will change dynamically with a request # which will be provided to my function. I only want to update the host name in this API but requiring me to feed a bunch of other attributes such as username, schema name, port, database type, connector name, etc. We were hoping not to have to feed that many variables to update a connector with unchanged information.
Behind the scenes it looks like Delphix Masking engine views the details of the job, ruleset and connector, creates a new one on the fly then deletes the old connector. Would we have to do the same thing?
------------------------------
Robert L. Henning
Enterprise Platforms - Technology Services - Senior Associate
Enterprise Databases
------------------------------