i'm not sure i would call that github project "dynamic" (maybe "cloudflare-gen-bindings")? Regardl
i'm not sure i would call that github project "dynamic" (maybe "cloudflare-gen-bindings")? Regardless - cool hack.
I wish there was an open discussions page to discuss requests and future direction?
Besides being able to dynamically create resources, it would also be nice to build some higher-level abstractions (at least for common usecases), to help simplify the management.
For example, it would be great if there was some form of higher-level "sharding" support that only required a resource to be configured with a "sharding key" (Example: A D1 "foobar" db shared by "customer_id"). That resource (D1, or Queue, or ...) would then require the shard-key to operate on it.
Under the covers Cloudflare would then manage "foobar" by appropriately creating a D1 instance when a new key is referenced, or finding/binding the instance when it does exist, and Migrations could also be done across the entire "foobar" cluster?
I wish there was an open discussions page to discuss requests and future direction?
Besides being able to dynamically create resources, it would also be nice to build some higher-level abstractions (at least for common usecases), to help simplify the management.
For example, it would be great if there was some form of higher-level "sharding" support that only required a resource to be configured with a "sharding key" (Example: A D1 "foobar" db shared by "customer_id"). That resource (D1, or Queue, or ...) would then require the shard-key to operate on it.
Under the covers Cloudflare would then manage "foobar" by appropriately creating a D1 instance when a new key is referenced, or finding/binding the instance when it does exist, and Migrations could also be done across the entire "foobar" cluster?
