feat: Use Localtunnel to improve developer experience #259
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.