specification
specification copied to clipboard
serverlessworkflow
Serverless Workflow Specification
**What would you like to be added**: Generate modern uses cases for the DSL. **Why is this needed**: Provide newcomers with high level use cases of what can be achieved...
**What would you like to be added**: Translate/optimize pre `1.0.0-alpha1` examples. Examples, like everything else, should be written in YAML, for the sake of readability and to leverage at best...
Currently we can write ``` set: name: Javi ``` or ``` set: name: ${.input.name} ``` However $ is a reserved keyword in JQ and {} are used in json, think...
**Please specify parts of this PR update:** - [ ] Specification - [ ] Schema - [ ] Examples - [ ] Extensions - [ ] Use Cases - [...
## What Would You Like to See Added? Introduce a new `containers` property to the workflow's resources. ## Why Is This Needed? Currently, both `shell` and `script` processes are expected...
### Discussed in https://github.com/serverlessworkflow/specification/discussions/978 Originally posted by **matthias-pichler** August 19, 2024 Currently the default output behavior for the `call: http` task is `content` which returns the content (i.e. body) of...
**Please specify parts of this PR update:** - [x] Specification - [x] Schema - [x] Examples - [ ] Extensions - [ ] Use Cases - [ ] Community -...
**What would you like to be added**: As discussed in #928, there are a few use cases where metadata information is useful such as when designing a graphical interface for...
**Please specify parts of this PR update:** - [x] Specification - [x] Schema - [ ] Examples - [ ] Extensions - [ ] Use Cases - [ ] Community...
**What would you like to be added**: Currently the DSL states for the [switch case](https://github.com/serverlessworkflow/specification/blob/main/dsl-reference.md#switch-case) that: `when` > A runtime expression used to determine whether or not the case matches....