Install
Works with Drupal: ^11Using Composer to manage Drupal site dependencies
Alternative installation files
Download tar.gz
44.21 KB
MD5: 286b6ed6a8f6a42868e259f849789e2d
SHA-1: f556051aa1a59fc69a392e8e768151f17ef76df3
SHA-256: 618a4c0d5dcec2357ec431f5443731937681c491f9ead0c26d68bd6501eb215c
Download zip
68.15 KB
MD5: bf4d85965574257e7f06eb438180e1cc
SHA-1: f809a286440179ab306ac0f568cd260956e6da24
SHA-256: cf53d73cc9c61f60d7784b78657b8184a4a066fd0452ff4cbd8299caf9a26f92
Release notes
FlowDrop Tool Provider now runs tools through Tool API's runner, as the user who started the run. Requires Tool API 1.0.0-beta12 and FlowDrop 2.7. Sites that cannot move to those versions stay on 1.0.0-alpha2; Composer will not offer them this release.
Before you upgrade
- Who a tool runs as. Runs started through FlowDrop's launch API or by a trigger now run their Tool API nodes as the user who started the run, also when the run is processed by a queue worker, where they used to run as anonymous. A trigger-started run acts as the user whose action fired the trigger; timer and cron triggers still act as anonymous. Workflows that failed on missing permissions may start working, and a run whose starter account was deleted now stops with
access_denied. Runs that record no starter (Playground, sessions, the editor's Run) behave as before. - Run
drush updbafter updating (or rebuild caches). Workflow tools refuse every caller until their cached definitions are rebuilt.
Changed
- Tool API nodes hand the call to Tool API's runner (
tool.runner). It checks the tool's declared permission before any input is processed, reports every invalid input at once, and keeps the reason when access is denied. - Tools see FlowDrop as the invoker
flowdropinstead of the genericphp. - A failed Tool API node returns an
erroroutput the editor can wire:access_denied,validation_error,tool_failureorexecution_error. Messages are plain text. - Workflow tools declare the
trigger flowdrop workflowspermission on their definition, so callers that list tools can see it.
Fixed
- Workflow tool inputs and outputs keep working when Tool API removes the
multipleconstructor argument. - An unexpected error in a Tool API node or a workflow tool is logged in full; the result names only the exception type.
- Refused tool inputs are logged at info level instead of warning.
Full details are in CHANGELOG.md.