In Harness, this behavior is usually by design, not a bug. Why the UI hides the input
D
Dew Viper
In Harness, this behavior is usually by design, not a bug.
Why the UI hides the input
When a variable (for example, configVar, appName, artifactTag, etc.) is defined inside a Step Group that is embedded in a Stage Template, Harness often treats it as an internal template input rather than a stage-level runtime input.
As a result:
✅ The value exists in YAML.
✅ The pipeline executes using the value.
✅ You can edit it in YAML view.
❌ It does not appear as a separate field in the Run Pipeline form.
❌ It may not appear in the visual pipeline editor.