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. If any connections do not exist, you can choose to import the pipelines or fragments without connections. After the import, you must edit the pipelines or fragments to define the 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.