On April 28, 2021, Google changed the required permissions for attaching IAM roles to service accounts. If you are using IAM roles for your Google service accounts, please see Changes to User Management.
Review the changes to the publicly available REST APIs for Dataprep by Trifacta® for the current release and past releases.
Changes for Release 8.2
Changes for Release 8.1
Customize relational connectors via API
Beginning in Release 8.1, you can customize aspects of each relational connection type available in your product edition through a set of APIs. Some terms:
- connection: In the Trifacta applicationand via API, you can create and manage connections between the platform a specific datastore. A connection is the user-defined object that enables the connection to the datastore.
connector: A connection interfaces with a connector, which is an underlying driver and its related configuration, that perform the actual connection. This configuration information includes runtime, publishing, and connection definitions.
Tip: All connections of the same type use the same underlying connector, including its configuration. Overrides that you apply to a connector apply to all current and new connections of that type in the workspace.
Get connector identifier
To use these API endpoints, you must acquire the connector identifier. This value is the
vendor value for a connection of the type. You can acquire this value in one of two ways:
Create a connection of the type in the Trifacta application. Use the
/v4/connections/:idendpoint with the GET method to acquire the connection information for your connection. Acquire the
vendorvalue. Dataprep by Trifacta API Reference docs: Premium | Standard
- You may find the
vendorvalues listed in the documentation. See Connection Types.
Get connector metadata information - defaults
The following endpoint returns the default metadata information for a specified connector type. This information is stored in the Connector Configuration Service database.
:connectorId value below, use the
vendor value that you acquired above. For example, to acquire connector type definitions for MySQL connection type, use the value
|Description||Get the default metadata for a connector without applying custom overrides. This metadata is used to defined connectivity, ingestion, and publishing for the connector.|
Get connector metadata information - current values
The following endpoint acquires the current metadata for a specified connector type, which include the default values with any applicable overrides applied to them.
|Description||Get the consolidated metadata for a connector in a given workspace. This metadata is used to defined connectivity, ingestion, and publishing for the connector.|
Get connector metadata information - get overrides values
The following endpoint retrieves the overrides that have been applied to a specific connector.
|Description||Get the metadata overrides for a connector in a given workspace. These overrides are applied to the base configuration for connectivity operations.|
Create overrides for a connector
The following endpoint applies the specified value or values as overrides to the connector.
The specified overrides are merged into the current set of overrides for the connector. A new entry is created if no overrides currently exist.
Delete overrides for a connector
The following endpoint deletes all override values for a specified connector.
All overrides are deleted. The connector reverts to the base configuration.
Asset transfer API using email addresses
You can now transfer all assets owned by one user to another user.
NOTE: This feature is available to project owners only.
- When a user transfer assets, the level of privilege (viewer, editor, or owner) is transferred with each asset. It is technically possible for a user to own an asset and to have sub-maximal privileges on the asset.
- For shareable assets such as flows and connections, the original owner is downgraded to editor of those assets and any assets scoped within them, such as datasets.
- Schedules are transferred. Time and time zone information in the schedules are not modified during the transfer.
- For non-shareable assets, such as folders and macros, the original owner no longer has access to them at all.
- Participants in the transfer can be identified by email address or internal identifier of the platform.
- Transferring of assets does not check for access to the objects. It's possible that the receiving user may not be able to access connections or datasets that were created by the original user. Examples:
- Original user accessed data through a connection that was shared to the user. Receiving user does not have access to or credentials for the connection.
- Original user had permissions to directories on the backend datastore that the receiving user does not have.
- This endpoint does not delete the user who transferred the assets.
Here is the mapping of example user identifiers:
|role||email address||internal identifier|
Transfer of assets using email:
|Response Status Code|
Transfer of assets using internal identifier:
The following endpoint call transfers assets from userId
4 to userId
|Response Status Code|
Changes for Release 7.5
Flow sharing API now accepts user email addresses
Beginning in Release 7.5, the API has been enhanced to allow insertion of a user's email address as part of the request body. Below is an example request:
If the above returns a
201 - Success status message, then
email@example.com has been given the role of
collaborator, which uses the
flow_editor policy, for flowId
This page has no comments.