feat: webhook workers

[steebchen]

Description

fix #347

Type of change

• New feature (non-breaking change which adds functionality)

What's Changed

TODO

• webhook request check (mark step as failed if webhook returns non-200)
• basic healthcheck (call API route before starting)
• advanced healtcheck (ping continuously and take down worker if more than 3 failed healthchecks)
• change action names to get from healthcheck instead of query
• return response only once stuff is processed
• do not require workflow IDs to be specified in registerWorkflow (or UI), do that automatically instead
• think about: changing workflows (with their actions) or assigning new workflows to webhook workers, and killing existing ones/re-creating (internal note: check both worfklows and actions (via workflow hash?) and re-create if needed)
• !!! the healthcheck needs to automatically update/register the workflow (it doesn't seem to be registering it the first time?)
  • Go client
    • requires refactor of .On->.RegisterWorkflow methods and signature
  • TS client
• TS client: check for signature as middleware
• !!! verify webhook secret in health endpoint to make sure it is set correctly before sending any events
• !! cleanup hardcoded env vars (token & tlsStrategy)
• !! do not re-create token every time
• investigate bug where no healthcheck requests are sent (might be invalid now, not sure)
• encrypt token
• rewrite queries to sqlc x)
• test services
• test register action
• delete webhook workers
  • (API & UI)
  • stop currently running workers
• add webhook worker name to DB and UI
• optional: vercel streaming or waitUntil

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
hatchet-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 25, 2024 8:42pm

[grutt]

good work.
a few minor nits and questions but probably nothing show stopping