pipeline: multi line string input?
complete
T
Tawny Aardvark
it's possible to have multi line string for pipeline input?
at the moment, the string input allow input as a giant string... but it's pretty hard to read, would be nice if we could have an option to enter multi line string for scenario where it's easier to enter data as a yaml content or just multi line text?
entering
Sudarshan Purohit
updated the status to
complete
Sudarshan Purohit
This feature is now available for all Pipeline and stage level variables, behind the Feature Flag PIPE_MULTILINE_VARIABLE_INPUT. Please file a support ticket to have this enabled for your account.
In case there are additional variables in specific steps that you need updated, please let us know through support and we can update those variables.
Gino Orvieto
Merged in a post:
Multi-line input set variables
T
Thistle Ocelot
We would like to submit a feature request for allowing input variables to be multi-line. Some of our inputs are JSON objects and it would be much easier for troubleshooting and implementation purposes if the input for those JSON variables were multi-line so we did not have to minify the JSON (often hiding subtle differences)
This post was marked as
in progress
T
Thistle Ocelot
Has there been any update on the question below, this has been unanswered for nearly a month now.
T
Thistle Ocelot
Any update on the question listed below?
T
Thistle Ocelot
Just to be sure, I'm asking for multi-line input (not output) variables. So when you are setting up an Input Set, the ability to have a multi-line text area. Is that what this feature flag would do?
F
Flamingo pink Shrew
Hey Michael,
This feature is behind the feature flag: CI_ENABLE_MULTILINE_OUTPUTS_SECRETS. Please reach out to your support team to enable this on your environment.
Here are some details on how we've implemented it:
Multiline Output Variables: CI steps support multiline output variables, including special characters such as \n, \t, \r, \b, maintaining shell-like behavior.
Complete Output Support: Output variables support both output secrets and output strings.
JSON Preservation: JSON data can be passed as-is without automatic minification.
Increased Output Variable Capacity: The maximum output variable size is approximately 131,072 characters, up from 65,536.
Some known technical limitations to consider as you use this feature:
The maximum size of output variables is constrained by the operating system's ARG_MAX parameter, which limits command line arguments and environment variables.
Exceeding this limit will result in the error:
fork/exec /bin/sh: argument list too long
This is actually implemented by the OS and not a feature limitation
Thank you
Regards
Shivkumar Loka
Harness Product Team
Autopilot
Merged in a post:
Multiline input
P
Previous Falcon
Hi Team,
I have a variable that contains multiline content. I believe that if a variable is multiline, its corresponding input type should be a text area. However, I do not see such an option in the available dropdown menu.
Could you please assist me in enabling this feature or provide guidance on how to implement it
Rohan Gupta
Merged in a post:
Add Multi-Line Text Area for Pipeline Inputs
T
Teal blue Mackerel
Summary:
When configuring pipeline variables to accept YAML or other lengthy input, the current single-line input box is impractical and cluttered. Providing a multi-line text area—or an expanded code-like editor—on the “Run Pipeline” window would improve usability and reduce input mistakes.
Problem Statement / Pain Point:
Large YAML or JSON content is difficult to edit and review in a cramped single-line field.
Users are more prone to syntax errors or formatting mistakes due to limited space.
The current flow diminishes productivity by forcing repeated scrolling or external text editors.
Proposed Solution:
Replace the single-line input with a multi-line text area that automatically expands, or add a toggle to switch to a code editor view.
Offer basic formatting or syntax-highlighting to ease reading and editing.
Benefits / Impact:
Improves user experience by making it simpler and quicker to provide or adjust complex inputs.
Decreases errors and rework caused by formatting issues.
Streamlines the pipeline setup process for teams working with large YAML configurations.
Load More
→