-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
🐛 Ensure that webhook server is thread/start-safe #1225
🐛 Ensure that webhook server is thread/start-safe #1225
Conversation
This ensures that the webhook server is both threadsafe & "start-safe" -- i.e. you can register webhooks after starting the server. While this is generally not a common pattern, be allow runnables to be added to the manager after start, so it makes sense to do the same with hooks & the server.
/assign @vincepri |
Ping - can someone please approve this? Thanks! |
/assign @DirectXMan12 ? |
/milestone v0.6.x |
/lgtm |
/retitle 🐛 Ensure that webhook server is thread/start-safe |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: adrianludwin, alvaroaleman The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
This is a cherrypick of #1155 into the v0.6 branch. I tested it by importing this (modified) branch into HNC and verifying that it solved the problem (kubernetes-retired/multi-tenancy#1127).
Fixed #1172.
The original description follows:
This ensures that the webhook server is both threadsafe & "start-safe"
-- i.e. you can register webhooks after starting the server. While this
is generally not a common pattern, be allow runnables to be added to the
manager after start, so it makes sense to do the same with hooks & the
server.