Create a list of value-based import rules for the specified deployment. Delete any previous rules applied to the same values.
NOTE: Import rules must be applied to individual deployments.
The generated rules apply to all flows that are imported into the Production instance after they have been created.
NOTE: Deployments pertain to Production instances of the Trifacta® platform. For more information, see Overview of Deployment Manager.
The response contains any previously created rules that have been deleted as a result of this change.
You can also make replacements in the import package based on object references. See API Deployments Object Import Rules Patch v4.
NOTE: Each request to the Trifacta® platform must include authentication credentials. See https://api.trifacta.com/ee/6.0/index.html#section/Authentication.
|Internal identifier for the deployment|
Request URI - Example:
Request Body Example: Single value replacement
The following JSON array describes a single replacement rule for the S3 bucket name. In this case, the
wrangle-dev bucket name has been replaced by the
wrangle-prod bucket name, which means data is pulled in the Production deployment from the appropriate S3 bucket.
NOTE: The executing user of any job must have access to any data source that is remapped in the new instance.
Request Body Example: Multiple value replacements
The following JSON array describes two replacements for the
fileLocation values. In this case, rules are applied in succession.
NOTE: Rules are applied in the listed order. If you are applying multiple rules to the same object in the import package, the second rule must reference the expected changes applied by the first rule.
In the above:
- The first rule replaces the string
klamathin the path to the source with the following value:
- The second rule performs a regular expression match on the string
/dev/. Since the match is described using the regular expression syntax, the backslashes must be escaped. The replacement value is the following literal:
You can specify matching values using the following types of matches:
|Match Type||Example Syntax|
NOTE: Use of Trifacta patterns is not supported.
For more information on patterns, see Text Matching.
Response Status Code - Success:
200 - OK
The response body contains any previously created rules that have been deleted as a result of this update.
Response Body Example: All new rule, no deletions
If the update does not overwrite any previous rules, then no rules are deleted. So, the response looks like the following:
Response Body Example: Replace file location, delete previous rule
If you submit the request again, the response contains the rule definition of the previous update, which has been deleted.
|id||Internal identifier for the value import rule|
The type of value import rule:
|on||The specified literal or pattern to match.|
|with||The replacement value or pattern|
|createdAt||Timestamp for when the rule was created|
|updatedAt||Timestamp for when the rule was last updated|
|creator.id||Internal identifier of the user who created the rule|
|updater.id||Internal identifier of the user who last updated the rule|
|deployment.id||Internal identifier for the deployment from which the import rule was deleted.|
This page has no comments.