-
Notifications
You must be signed in to change notification settings - Fork 770
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
feat: bind to an external script's durable object by environment #996
Labels
enhancement
New feature or request
Comments
threepointone
added a commit
that referenced
this issue
May 16, 2022
For durable objects, instead of just `{ name, class_name, script_name}`, this lets you bind by environment as well, like so `{ name, class_name, script_name, environment }`. Fixes #996
threepointone
added a commit
that referenced
this issue
May 16, 2022
For durable objects, instead of just `{ name, class_name, script_name}`, this lets you bind by environment as well, like so `{ name, class_name, script_name, environment }`. Fixes #996
Repository owner
moved this from In Review
to Done
in workers-sdk
May 16, 2022
threepointone
added a commit
that referenced
this issue
May 16, 2022
For durable objects, instead of just `{ name, class_name, script_name}`, this lets you bind by environment as well, like so `{ name, class_name, script_name, environment }`. Fixes #996
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A durable object binding (external) looks like this
{ name, class_name, script_name}
, but should also optionally acceptenvironment
so as to be{ name, class_name, script_name, environment }
. This should probably only work with service environments (with legacy, you'd add-<env>
to thescript_name
)The text was updated successfully, but these errors were encountered: