Current Behavior: The notification channel URL field currently only accepts secrets as input expression However, in our organization, the use of secrets is restricted, leaving us with no dynamic option to configure notification channel URLs.

Desired Behavior: We would like the notification channel URL field to also support Harness variables as a valid input expression , providing a viable alternative to secrets.