Current Limitation: The Harness IDP trigger:harness-custom-pipeline action currently only resolves inputsets through pipeline/stage variable paths (FQNs) for template-backed pipelines. It cannot directly bind to deployment specification nodes such as spec.serviceInputs.serviceDefinition.spec.variables[].environmentRef.

Problem: When using stage templates with Service/Environment selectors modeled as runtime inputs, IDP cannot bind these values directly at trigger time. This forces developers to implement workarounds by:

Creating serviceRef and environmentRef as pipeline-template runtime variables

Manually mapping them internally to the stage template's serviceInputs and environmentInputs

Requested Enhancement: Enhance the trigger:harness-custom-pipeline action to natively support direct binding of Service/Environment runtime template inputs in template-driven CD pipelines.