Feature/workflow - #50
Merged
Merged
Conversation
Make new workflows Prefect-only and separate worker dependencies. Bind execution history to published versions and immutable step snapshots. Use local list queries with serialized five-second frontend polling. Add administrator-managed API target allowlisting and runtime policy checks.
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
![github-code-quality[bot]](https://avatars.githubusercontent.com/u/9919?s=60&v=4){kind=small}
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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 PR isolates workflow execution in Prefect and adds node-level progress updates through Worker → Prefect Server → Django → frontend, removing the worker’s dependency on Django ORM and the application database.
workflows/prefect/, remove legacy execution paths, and make new workflows Prefect-only.PREFECT_WORKER_TOKENsetup.Deployment requires the new database migrations, updated backend/worker dependencies, and the new Prefect flow entry point. Django and workers must share the workflow encryption keys. Existing local workflows need republishing; legacy
send_webhooknodes should migrate to API Call with approved targets configured.Validated locally with 124 backend tests, real Prefect-to-frontend progress delivery, and HTTP-triggered consumer startup. The local test files are not included in these two commits.