Skip to content

Conversation

buehler
Copy link
Collaborator

@buehler buehler commented Aug 19, 2021

This closes #253. When developing webhooks, one needed to
start the operator locally, then use some technology like "localtunnel"
or "ngrok" to have a tunnel (with HTTPS) to the local running operator
and then register that given randomized url to Kubernetes to
actually call the migrator/validator.

This pull request uses localtunnel as a libary by adding AddWebhookLocaltunnel
to the operator builder. With this, the operator creates a localtunnel
during startup and registers itself within Kubernetes with the returned url.

Note: this should never be used in production.

@buehler buehler changed the base branch from master to next August 19, 2021 11:27
@buehler buehler merged commit b94c592 into next Aug 19, 2021
@buehler buehler deleted the feat/localtunnel-integration branch August 19, 2021 11:41
@github-actions
Copy link

🎉 This PR is included in version 5.1.0-prerelease.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

buehler added a commit that referenced this pull request Aug 19, 2021
This closes #253. When developing webhooks, one needed to
start the operator locally, then use some technology like "localtunnel"
or "ngrok" to have a tunnel (with HTTPS) to the local running operator
and then register that given randomized url to Kubernetes to
actually call the migrator/validator.

This pull request uses localtunnel as a libary by adding AddWebhookLocaltunnel
to the operator builder. With this, the operator creates a localtunnel
during startup and registers itself within Kubernetes with the returned url.

Note: this should never be used in production.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Improve Webhook Developer Experience with Localtunnel

1 participant