Hello Harness Team,

As part of our extensive use of Harness override declarations across multiple deployment scenarios, we have encountered increasing challenges related to troubleshooting and configuration validation during pipeline execution.

Currently, Harness prints a list of variables during deployment execution under Service / Service Overrides in the console logs. While this is helpful, it does not provide sufficient detail to efficiently diagnose issues when a variable value is missing or incorrectly configured. In addition, determining which override level (e.g., environment, service, infrastructure) ultimately resolved a variable requires additional manual effort.

To improve observability and streamline troubleshooting, we propose enhancing the execution logs to include the following information for each resolved variable:

Variable name

Resolved value

Effective scope

Source override level (e.g., Global, Environment, Service, Infrastructure)

Providing this information directly in the Harness console logs would significantly reduce troubleshooting time, improve transparency during deployments, and help users quickly identify misconfigurations or unintended overrides.