[BUG] Cannot create binding for class in script '[script-name]' that does not exist.

I believe I have found a bug regarding defining durablje objects bindings from specific environments.
"durable_objects": {
"bindings": [
{
"name": "DATA_MIGRATION_PROCESSOR",
"class_name": "DataMigrationProcessor",
"script_name": "datamigration-processor-production",
"environment": "production",
},
]
}
"durable_objects": {
"bindings": [
{
"name": "DATA_MIGRATION_PROCESSOR",
"class_name": "DataMigrationProcessor",
"script_name": "datamigration-processor-production",
"environment": "production",
},
]
}
I need to add the -production to the script name even though the script name does not include -production and it's added by the fact I'm deploying the durable object with an --env parameter. I would figure that adding environment property would add the -production automatically. Is this a bug or it's meant to be that way?
0 Replies
No replies yetBe the first to reply to this messageJoin

Did you find this page helpful?