Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide actionable suggestions for when webhooks are not configured #2849

Merged
merged 6 commits into from
Jun 17, 2024

Conversation

davidmrdavid
Copy link
Contributor

@davidmrdavid davidmrdavid commented Jun 12, 2024

We periodically receive questions about apps failing with the following error "Webhooks are not configured". This often occurs when running in K8s environments.

This PR augments our error message to provide guidance on how to work around this error.

@@ -1241,7 +1241,9 @@ internal HttpCreationPayload GetInstanceCreationLinks()

internal Uri GetWebhookUri()
{
return this.webhookUrlProvider?.Invoke() ?? throw new InvalidOperationException("Webhooks are not configured");
string errorMessage = "Webhooks are not configured. This may occur if the environment variable `WEBSITE_HOSTNAME` is not set (should be automatically set for Azure Functions). " +
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit on <ip-address>:<port> - should we instead use something around "URI" wording? So it is more clear it is open to ip-address:port or a DNS name

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good idea - implemented in commit: 3621b12

@davidmrdavid davidmrdavid merged commit 9ef79cd into dev Jun 17, 2024
20 checks passed
@davidmrdavid davidmrdavid deleted the dajusto/improve-webhooks-error-message branch June 17, 2024 21:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants