specification
specification copied to clipboard
serverlessworkflow
Serverless Workflow Specification
**Please specify parts of this PR update:** - [x] Specification - [x] Schema - [ ] Examples - [ ] Extensions - [ ] Use Cases - [ ] Community...
**What would you like to be added**: Add a new `until` (optional) property to Event Consumption Strategies of type `any` **Why is this needed**: Allows authors to define streaming-like event...
**What would you like to be added**: Add a new property used to determine whether or not to await the execution of a process **Why is this needed**: Allows authors...
Signed-off-by: Matthias Pichler **Please specify parts of this PR update:** - [x] Specification - [ ] Schema - [ ] Examples - [ ] Extensions - [ ] Use Cases...
**What would you like to be added**: Extend CICD validation to CTK features **Why is this needed**: CTK features are not validated by the CICD pipeline, which creates multiple problems...
**What would you like to be added**:  currently `$secrets` is documented to be available everywhere, but I know @cdavernas mentioned it should only be...
**What would you like to be added**: Introduce a new `authorization` argument in runtime expressions. **Why is this needed**: This enhancement would enable tasks to utilize authorization credentials that have...
**What would you like to be added**: Add a property to configure the lifetime of spawned containers. **Why is this needed**: Gives authors the ability to decide whether or not...
**What would you like to be added**: Currently the output of the `fork` task is undocumented. My understanding is that: 1. `compete: false`: an array of the outputs from each...
**What would you like to be added**: Something I missed in the PR #995 that introduced the `await` property is to define what the (raw) output of a task with...