Summary: Enable users to define timeout parameters as runtime inputs at the pipeline template level, allowing individual consumers of the template to configure the timeout value based on their specific requirements. Background: Currently, in Harness, timeout parameters can only be defined as runtime inputs for stages or steps. For pipeline templates, timeout values must be hardcoded as plain text. This limitation creates challenges for teams with diverse needs, as the same timeout value might not be suitable across different use cases. Use Case: One app team recommends a 72-hour timeout for their pipeline, while other teams prefer the default timeout value. The inability to set timeout as a runtime input at the pipeline template level forces teams to create separate templates or modify individual pipelines, which is inefficient and error-prone. Proposed Solution: Allow timeout parameters to be defined as runtime inputs within pipeline templates. This would: Provide flexibility for template consumers to customize timeout values without modifying the template. Reduce duplication of templates for scenarios requiring different timeout configurations. Simplify the pipeline creation and management process. Benefits: Improved Flexibility: Teams can configure timeout values that suit their specific needs without modifying templates. Efficiency Gains: Reduces the need to maintain multiple templates for similar pipelines. Consistency: Centralized templates remain consistent, with configuration flexibility delegated to the pipeline level. Workaround: The current workaround is to configure timeout values directly in each pipeline after consuming the template. However, this adds manual overhead and is not ideal for large-scale operations.
