Repository navigation
Procedures: Mark unstable for initial release #3644
Description
In the module bindings libraries, feature-flag the procedure methods behind our unstable feature for the initial release.
Metadata
Metadata
Assignees
Labels
No labels
Activity
gefjon commentedon Nov 13, 2025
Also move the
/v1/database/:name/procedure/:funcroute under theunstablepath component, unless #3659 is already done.aasoni commentedon Nov 18, 2025
@gefjon just wanted to bring up that we have a proposal for reworking the database naming system. This would allow slashes in database names.
This is relevant for this ticket because of this section in the proposal.
the tl;dr is that for database slashes to work, existing APIs under database/:name_or_identity will require url encoded slashes which is not great user experience. A new set of APIs are proposed to mirror functionality but moving the :name_or_identity url parameter to the end to avoid ambiguous routing.
E.g.
database/:name_or_identity/reducer/:name -> database/reducer/:name_or_identity/:name
If the proposal is approved (happy for your input as well) new api end points under database/ should follow the new scheme so that they can support database with / in the name.
gefjon commentedon Nov 19, 2025
@aasoni some time after moving it under
unstable, we intend to remove the separate procedure route in favor of making/v1/database/:name/call/:funcable to transparently invoke both reducers and procedures.Add procedure HTTP request API for WASM modules and the Rust module b…
Rename the `/database/procedure` route to be `unstable` (#3723)