You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today we allow you to specify a certain set of passthrough modules when configuring the sandbox runner, but it only works if you know the module name (but it is hierarchical). Some users may want to pass through everything regardless of root module, so we should probably add a SandboxRestrictions field for passthrough_all_modules: bool.
The text was updated successfully, but these errors were encountered:
This is helpful because it still allows the sandbox to provide state isolation for each workflow, but without requiring users to worry about allow-listing individual modules as being deterministic.
cretz
added a commit
to cretz/temporal-sdk-python
that referenced
this issue
Jan 17, 2025
Describe the solution you'd like
Today we allow you to specify a certain set of passthrough modules when configuring the sandbox runner, but it only works if you know the module name (but it is hierarchical). Some users may want to pass through everything regardless of root module, so we should probably add a
SandboxRestrictions
field forpassthrough_all_modules: bool
.The text was updated successfully, but these errors were encountered: