-
Notifications
You must be signed in to change notification settings - Fork 11
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
Epic: Runtime Engine #393
Labels
Comments
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
TODO validate incoming workflows/attempts to make sure they're what we expect. This is good practice generally but more interestingly it'll keep the worker honest. On that note, the worker should do some validation too on the incoming attempts |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
Closing this down as it's no longer useful - the work has been done or branched off |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Epic to track the work needed in the multi-process runtime worker.
Remember we don't have a good name for this (runtime manager is insufficient). See #374. Runtime Worker might be useful.
Essential
@openfn/
modules #372Useful
Optional
To close
Not in issues
Stuff that needs doing that we don't have issues for
sanitize
log flagSecurity?
Security considerations for the actual process worker are more to do with not allowing malicious code to run and not allowing other environments/processes/jobs to be read. A lot of the security is subsumed by the enclosing server.
The text was updated successfully, but these errors were encountered: