Importing Objects

You can import pipelines, fragments, jobs, and topologies that were exported from Control Hub.

You can also import pipelines exported from a Data Collector or Transformer that is not registered with Control Hub.

Note: You can also export and import pipelines from registered execution engines. However, when an execution engine is registered with Control Hub, it's simplest to publish the pipelines directly to Control Hub.

Importing Pipelines

You can import pipelines from individual pipeline files or from an archive ZIP file. Pipeline files are JSON files exported from Control Hub, Data Collector, or Transformer.

Important: To import pipelines that use connections or to import pipelines with dependent fragments that use connections, the connections must already exist in the target organization.

When you import a single pipeline, you can rename the pipeline during the import. When you import a set of pipelines, Control Hub imports the existing pipeline names.

When pipelines include fragments, importing pipelines also imports any fragments used in the pipelines with the existing fragment names.

If necessary, you can rename objects after the import.

  1. In the Navigation panel, click Pipeline Repository > Pipelines.
  2. Click the Import icon: .
  3. Click one of the following tabs:
    • Import Pipeline - Use to import an individual pipeline.

      Enter a pipeline name and commit message, and then select the JSON file to import.

    • Import from Archives - Use to import one or more pipelines from a ZIP file. Must also be used to import pipelines that use connections.

      Optionally enter a commit message to be used for all imported pipelines. If not entered, Control Hub uses the individual commit message exported with each pipeline.

      Then, select the ZIP file containing the pipeline files to import.

  4. Click Import.

Importing Fragments

You can import fragments from individual fragment files or from an archive ZIP file. Fragment files are JSON files exported from Control Hub.

Important: To import pipeline fragments that use connections, the connections must already exist in the target organization.

When you import a single fragment, you can rename the fragment during the import. When you import a set of fragments, Control Hub uses the existing fragment names. If necessary, you can rename fragments after the import.

  1. In the Navigation panel, click Pipeline Repository > Pipeline Fragments.
  2. Click the Import icon: .
  3. Click one of the following tabs:
    • Import Pipeline Fragment - Use to import an individual fragment.

      Enter a fragment name and commit message, and then select the JSON file to import.

    • Import from Archives - Use to import one or more fragments from a ZIP file. Must also be used to import fragments that use connections.

      Optionally enter a commit message to be used for all imported fragments. If not entered, Control Hub uses the individual commit message exported with each fragment.

      Then, select the ZIP file containing the fragment files to import.

  4. Click Import.

Importing Jobs

You import jobs and job templates from an archive ZIP file containing job files. Job files are JSON files that contain the job or job template and the dependent pipeline and fragments exported from Control Hub.

Important: To import jobs with dependent pipelines or fragments that use connections, the connections must already exist in the target organization.

When you import a job or job template, Control Hub imports the existing names for the job, the dependent pipeline, and any fragments used by the pipeline. If necessary, you can rename objects after the import.

  1. In the Navigation panel, click Jobs.
  2. Click the Import icon: .
  3. Select the properties to import with the jobs.
    For the initial import of a job, you'll most likely want to select all properties.
    When you select the Pipeline property, the import includes all pipelines and any fragments used in the pipelines.
    Note: If you clear the Pipeline property for the initial import of a job, Control Hub still imports the dependent pipeline and any fragments used in the pipeline. Jobs must include a pipeline.

    For subsequent imports of a job that already exists in the target organization, you'll want to clear the properties that you have modified in the target organization. Any selections that you make overwrite the configured job properties in the target organization.

  4. Select the ZIP file containing the job files to import.
  5. Click Import.

Importing Topologies

You import topologies from an archive ZIP file containing topology files. Topology files are JSON files that contain the topology and the dependent jobs, pipelines, and fragments exported from Control Hub.

Important: To import topologies with dependent pipelines or fragments that use connections, the connections must already exist in the target organization.

When you import a topology, Control Hub imports the existing topology name and the existing names for all dependent jobs, pipelines, and fragments. If necessary, you can rename the objects after the import.

  1. In the Navigation panel, click Topologies.
  2. Click the Import icon: .
  3. Select the properties to import with the dependent jobs.
    For the initial import of jobs, you'll most likely want to select all properties.
    Note: When you import a topology, Control Hub always imports the pipeline versions used by the dependent jobs and any fragments used in those pipeline versions.

    For subsequent imports of jobs that already exist in the target organization, you'll want to clear the properties that you have modified in the target organization. Any selections that you make overwrite the configured job properties in the target organization.

  4. Select the ZIP file containing the topology files to import.
  5. Click Import.