Objects that Use Connections

When you export objects that use connections or objects with dependent objects that use connections, Control Hub exports the connection metadata only. The metadata includes the connection ID, name, and type. Control Hub does not export the connection credentials or other configured values.

For example, when you export a pipeline that uses a connection, Control Hub exports the connection ID, name, and type used by that pipeline. When you export a job with multiple pipelines that use connections, Control Hub exports the connection ID, name, and type of all connections used by each pipeline.

When you import pipelines or fragments that use connections, Control Hub first attempts to find matching connections by ID, and then by name and type. For each connection that exists in the target organization, you can choose to use the existing connection or to replace the connection. For each connection that does not exist, you can choose how to replace the connection. After the import, you must edit the pipelines or fragments to define the details for any replaced connections.

To import jobs or topologies that use connections, the connections must already exist in the target organization. During the import, Control Hub first attempts to find matching connections by ID, and then by name and type. If any connections do not exist, then pipelines or fragments using those missing connections fail to import. Pipelines or fragments using existing connections import successfully.

Tip: When migrating objects from one organization to another organization, create connections with the same name and type in the target organization before you import the objects.

Replace Connections on Import

During the pipeline or fragment import process, Control Hub lists the connection type and name for each connection used in the pipeline or fragment.

You can choose whether and how to replace each connection as follows:

Use existing connection: Imports the pipeline or fragment so that it continues to use the existing connection.; Available only when the connection exists in the target organization.
Create a placeholder connection: Automatically creates a new connection of the same connection type named Placeholder for <original connection name>, updates the pipeline or fragment to use the placeholder connection, and then imports the pipeline or fragment. The new placeholder connection has no defined values. After the import, you must edit the placeholder connection to define the required properties.; For example, you import a pipeline that includes an Oracle CDC origin configured to use an Oracle connection named oracle_source. During the import, you choose to create a placeholder connection. Control Hub creates a new Oracle connection named Placeholder for oracle_source, but with no defined values. Control Hub updates the imported pipeline to use the new placeholder connection. After the import, you edit the Placeholder for oracle_source connection to define the required properties.; Available both when the connection exists and when it does not exist in the target organization.
Remove the connection: Imports the pipeline or fragment without the connection.; After the import, you must update the imported pipeline or fragment to select another existing connection or to directly enter the connection details in the pipeline or fragment.; For example, you import a pipeline that includes a Snowflake destination configured to use a Snowflake connection named snowflake_dev_target. During the import, you choose to remove the connection. After the import, you edit the pipeline and configure the Snowflake destination to use another existing Snowflake connection named snowflake_prod_target.; Available both when the connection exists and when it does not exist in the target organization.