Give each action a descriptive name to precede the job's output in the console.

Exact name of pending config data set for which the data should be exported

Use comma separated values for exporter variables

The SWEAGLE exporter to use when retrieving the config data.

Location of file within the Jenkins workspace to save the exported data.

Select the supported format of the file to be uploaded.

Sets a Jenkins Environment variable to value of a configuration data item. One variable on each line. format is colon seperated key value pair VARIABLE:Path.to.node.cdi Example: INTERNAL_IP:PRD.infra.db023.ipInternal

Mark the build as "Failed" should the data export fail.

Show the results of the API call in the Jenkins job console log.

Give each action a descriptive name to precede the job's output in the console.

Exact name of pending config data set for which the snapshot should be taken.

A description for the snapshot

Mark the build as "Failed" should the snapshot fail.

Show the results of the API call in the Jenkins job console log. Warning !!! The API results of a snapshot will include the entire Config Data set.

A single string as TAG for that snapshot - cannot contain spaces but can utilize Jenkins variable4s ex "release1.2.${BUILD_ID}"

Give each action a descriptive name to precede the job's output in the console.

Fullpath of file relatove to the Jenkins workspace using Ant file filter format for selecting multiple files with wildcard. Details here. Examples: myconfig.json *.json subdirectory/*.json

Select the supported format of the file to be uploaded.

Enter the path where the data should be uploaded. Separate the nodenames in the path with a comma. In case the nodes do not yet exist, they will be created automatically.

Allow Delete If checked will delete any nodes and MDIs that are not part of the upload. If the nodes are included or inherited the nodes and MDIs at points of inclusion will also be deleted unless "Only Parent" is also checked.

A description for the snapshot

Create Filename Nodes If checked, nodes will be created for all matching files names in the file location and file data will be placed under file name node.

Identifier Words To make nodes part of an array uniquely identifiable, a comma separated list of 'identifier words' can be added. If no identifierWords are provided, the behavior will default to the identifierWords listed in the find.identity_attributes_discovery.word_list preference

Mark the build as "Failed" should the data upload fail for any reason.

Only Parent This controls if in case the allowDelete flag is set to true if the deletion of nodes and CDIs will only happen at the node itself, or also at any other place where the node is included or in every child node that is inheriting.

Show the results of the API call in the Jenkins job console log.

Search Sub-directories If checked sub-directories will also be searched recursively for matching files.

A single string as TAG for that snapshot - cannot contain spaces but can utilize Jenkins variable4s ex "release1.2.${BUILD_ID}"

Allow Delete If checked will delete any nodes and MDIs that are not part of the upload. In case the nodes are included or inherited, also the nodes and MDIs at points of inclusion will be deleted

Only Parent If checked will delete any nodes and MDIs that are not part of the upload. In case the nodes are included or inherited, also the nodes and MDIs at points of inclusion will be deleted

Store Snapshot. This controls if automatically a snapshot should be created for each of the impacted config data sets by this data upload.

Give each action a descriptive name to precede the job's output in the console.

The exact name of the config data set which should be validated.

Fail build on validate errors. Set thresholds used to determine if the build should be failed based on the number of validation errors or warnings.  Use -1 to ignore either threshold.

Fail build on validate errors or if the pending data set fails to show up after all the retry attempts have completed.

Fail build if no data is found for the Config Data Set (CDS).

Number of retry attempts while waiting for a pending config data set. Combined with with Retry Interval to force a timeout after attempts have completed. Use "-1" for unlimited retries.

Number of seconds between each attempt to find a matching config data set for validation. Combine with with Retry Count to force a timeout after attempts have completed.

Show the results of the API call in the Jenkins job console log.

Validate the stored snapshot for the config data set instead of the pending data.

Fail build on validate errors. Set thresholds used to determine if the build should be failed based on the number of validation errors or warnings.  Use -1 to ignore either threshold.