Webhook trigger copy shows prod cluster URL instead of vanity cluster URL
G
Garnet Otter
Issue Summary:
When copying the webhook link from the Trigger Form in Harness, the generated URL points to the prod cluster URL instead of the vanity cluster URL. This is misleading for users because they expect the vanity domain to be used.
Expected Behavior:
The copied webhook URL should use the vanity cluster domain:
https://<vanity-cluster-url>/ng/api/webhook?accountIdentifier=<account-identifier>
Actual Behavior:
The copied webhook URL is generated as:
https://<prod-cluster-url>/ng/api/webhook?accountIdentifier=<account-identifier>
Impact:
This may confuse users and make it appear as though the webhook is tied to the wrong environment/domain.
Steps to Reproduce:
- Open the webhook trigger form in Harness.
- Copy the webhook link.
- Observe that the copied URL uses the prod cluster domain instead of the vanity cluster domain.
Additional Notes:
Please confirm whether this is expected behavior or a configuration/UI issue. If possible, update the copied webhook URL to reflect the correct vanity cluster