Describe the issue
We shouldn't be able to access /managed-workers in self-hosted version of the Hatchet app. Instead, when we do, we are just met with an infinite loading screen and the life spammed out of a page that DNE.
Also, subpages still exist so we can attempt to add a managed worker via /managed-workers/create 🤷
Environment
- Engine: Hatchet Lite v0.86.8
Expected behavior
Return a 404 or a dialogue saying this isn't supported in self-hosted mode.
Code to Reproduce, Logs, or Screenshots
Build the vite app, then launch hatchet lite i.e
cd frontend/app && pnpm install && npm run build
LITE_STATIC_ASSET_DIR=./frontend/app/dist LITE_FRONTEND_PORT=5173 task start-lite
Then, after seeding etc., accessing https://app.dev.hatchet-tools.com/tenants/707d0855-80ab-4e1f-a156-f1c4546cbf52/managed-workers should give you the following:
Additional context
Anything else that might help us understand or reproduce the problem — e.g. specific page URL, logged-in vs logged-out, related docs or workflows.
N/A
Describe the issue
We shouldn't be able to access
/managed-workersin self-hosted version of the Hatchet app. Instead, when we do, we are just met with an infinite loading screen and the life spammed out of a page that DNE.Also, subpages still exist so we can attempt to add a managed worker via
/managed-workers/create🤷Environment
Expected behavior
Return a
404or a dialogue saying this isn't supported in self-hosted mode.Code to Reproduce, Logs, or Screenshots
Build the vite app, then launch hatchet lite i.e
Then, after seeding etc., accessing
https://app.dev.hatchet-tools.com/tenants/707d0855-80ab-4e1f-a156-f1c4546cbf52/managed-workersshould give you the following:Additional context
Anything else that might help us understand or reproduce the problem — e.g. specific page URL, logged-in vs logged-out, related docs or workflows.
N/A