openapi: Add requestBody to runWorkflow #220
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kba
requested changes
Aug 16, 2022
|
I am unsure about the description but couldn't find a better one |
kba
approved these changes
Aug 16, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, I think, we only need the workspace_id (and the workflow_id provided in the path) to run a workflow. I think this is always required for other implementers as well. Please correct me if I am wrong. But I think that it is likely, that we or other implementers may encounter another parameter needed, like the starting file-grp for example. Because of that, I decided to add the
parameterssection like in processorArgs. I think this gives more flexibility to the implementers. Because I am not too sure about that please don't hesitate to comment if you have another opinion on that.