Clone Pipeline - Ironstream_Hub - ironstream_for_kafka - ironstream_for_elastic - ironstream_for_splunk - 1.3

Ironstream Hub Administration

Product type
Software
Portfolio
Integrate
Product family
Ironstream
Product
Ironstream > Ironstream Hub
Ironstream > Ironstream for Splunk®
Ironstream > Ironstream for Kafka®
Ironstream > Ironstream for Elastic®
Version
1.3
Language
English
ContentType
Administration
Product name
Ironstream Hub
Title
Ironstream Hub Administration
First publish date
2022

Field

Description

Usage:

Copies the configuration of one pipeline to one or more other pipelines as listed in a text file.

Arguments:

(required) -from (-from <pipelinename>)

(required) -to (-to <text file>)

Examples:

ihubcmd -clone-pipeline -from sysi.prcsly.com -to pipeline_list.txt

Expected Output:

A result message stating what the outcome of the clone pipeline command is. Such as:
  1. Command arguments are invalid.
  2. Unable to find the pipeline
  3. From pipeline is not valid for cloning
  4. To pipelines are not valid for cloning to
  5. An error occurred while cloning the pipeline. <error details>.
  6. The pipeline was successfully cloned.

Notes:

-from exactly matches the name of a valid and saved pipeline.

-to points to a text file containing the names of one or more pipelines that will receive the contents of the -from pipeline.

This text file must have a single pipeline name on each line to which the -from configuration will be applied.

Each pipeline name must begin in the left-most position of the line and must exactly match the case of an existing pipeline.

The source types in the list of -to pipeline does not need to match the -from pipeline.

The types and numbers of targets in each -to pipeline does not need to match the -from pipeline. These will be created or updated by the cloning operation.

Before any cloning takes place the conf directory will be copied to a dated and timed name of conf_backup_<datetime> and you will be prompted to confirm you wish to undertake the cloning. If once the clone completes successfully the results are not as you wish, you can rename the conf directory to, for example conf.old, then rename the just-created conf_backup_<datetime> directory to conf.