Input sets
Save and reuse runtime input values across pipeline runs using input sets and overlays.
Pipelines often run the same stages and steps but need different values across environments or scenarios. Pipeline inputs let you define those variable values as named parameters. Input sets and overlays let you save those values and reuse them across runs, so you do not re-enter the same configuration every time you run a pipeline.
Input set: a saved collection of values for a pipeline's inputs. Select an input set when running the pipeline and Harness pre-fills the inputs for you.
Overlay input set: a combination of multiple input sets applied together. Instead of maintaining monolithic configurations that repeat shared values, you build overlays from modular, reusable input sets.
What you will learn
How input sets save runtime input values so you do not re-enter them on every run
How to create, manage, and apply input sets from the Input Sets tab
How overlay input sets combine multiple input sets into a single reusable configuration
How input values are handled when rerunning a pipeline from a failed stage
Input sets
An input set is a named collection of values for a pipeline's inputs. You can create multiple input sets for the same pipeline, one per environment, service, or scenario, and select the right one at runtime.
Because pipelines with inputs prompt for values each time they run, input sets save those values so runs are consistent and repeatable. You do not need to remember or re-enter the same values for every run.
For example, you can create:
A dev input set with a development image tag and
dev.example.comas the target URL.A production input set with a stable release tag and
prod.example.com.
You do not have to fill every input in an input set. Leave fields empty to keep them as manual inputs that you fill at runtime.
Permissions
To create or edit input sets, you need Pipeline: Create/Edit permission. To run a pipeline with an input set, you need both View permission on the input set and Pipeline: Execute permission.
Create an input set
Select Input Sets in the pipeline header.
Click + Create input set.
In the Input Set panel, enter a Name. Harness suggests an Id automatically.
Under Input Set Type, select New input set.
Under Inputs, enter values for the pipeline inputs you want to pre-define. You do not need to fill every input. Leave fields empty to keep them as manual inputs at runtime.
Optionally add a Description and Tags under Metadata.
Click Add Input Set.
Use an input set
In Pipeline Studio, click Run.
In the Run Pipeline dialog, click + Add under Input Sets and select an input set.
Under Inputs, the pipeline inputs are shown with values pre-filled from the selected input set. You can edit any value before running.
Optionally select Skip preflight checks or Notify only me.
Click Run pipeline.
Required inputs with no pre-filled value must be filled before you can run.
Overlays
An overlay input set combines multiple input sets into one reusable configuration. Instead of duplicating shared values across input sets, you split your configuration into focused, modular sets and combine them in an overlay.
For example, for a CD pipeline that deploys multiple services to multiple environments, you might create:
Common: shared defaults used by every deployment, such as logging level, timeout values, or a notification email.
Service A: configuration specific to Service A, such as its image name and service endpoint.
Production: environment-specific overrides, such as replica count and resource limits.
Apply the Common + Service A + Production overlay to get the right combined configuration without duplicating values across every input set. Swap out Service A for Service B in a different overlay and reuse everything else.
When you run a pipeline with an overlay, Harness applies the input sets in order. If the same input is defined in multiple sets, the value from the last set wins. For example, if Common defines replicas: 1 and Production defines replicas: 5, the overlay resolves to replicas: 5 because Production is applied last.
Create an overlay
Select Input Sets in the pipeline header.
Click + Create input set.
Enter a Name. Harness suggests an Id automatically.
Under Input Set Type, select Overlay input set.
Under Input Sets, click + Add and select the input sets to include.
Arrange them in the order you want them applied. Input sets resolved later override values set by earlier ones.
Optionally add a Description and Tags under Metadata.
Click Add Input Set.
Use an overlay
Using an overlay follows the same steps as using an input set. In the Run Pipeline dialog, click + Add under Input Sets and select the overlay. Harness resolves the combined values from all input sets in the overlay and pre-fills the pipeline inputs for you.
When running with an overlay, you can choose which input sets from the overlay to include. Input sets you deselect are skipped for that run.
Rerun a pipeline
When you rerun a pipeline, how input values are handled depends on the rerun option you choose:
From Last Failed Stage: Harness reuses the input values from the original execution. Any input values you change before the rerun are not applied. The pipeline continues with the exact same inputs as the original run.
From Specific Stage: Harness reloads inputs for the selected stage. Updated input values apply for that stage and everything after it.
To use different input values on a rerun, select From Specific Stage.
Example: a pipeline ran with image tag v1.1.0. You rerun and update the image tag to v1.2.0 in the dialog. If you select From Last Failed Stage, the pipeline continues with v1.1.0. If you select From Specific Stage, the pipeline uses v1.2.0.
Next steps
Go to Pipeline settings to define inputs for your pipeline.
Go to Execution logs to view the inputs used in a specific run from the Inputs tab of any execution.
Last updated
Was this helpful?