Support for print() Debug Statements in Harness Policy Editor UI
under review
P
Protective Stingray
Requesting an improvement to the Harness Policy Editor experience to support visibility of print() debug statements during policy testing.
Current Behavior:
- The print() function, commonly used in Rego for debugging, does not currently surface any output in the Harness Policy Editor UI during test executions.
- As a workaround, users are embedding debug data into deny messages using sprintf(), which is functional but not ideal for iterative development.
Customer Expectation:
- The ability to see print() outputs in the Policy Editor UI when testing Rego policies. This would greatly enhance the debugging experience during policy creation and testing.
Impact:
- Developers and admins using the Harness Policy Engine face challenges during development due to the lack of visibility into intermediate values or logic flows in their Rego policies.
- This results in slower policy iteration, especially for more complex rules.
Log In
Prasad Satam
under review