We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
It would be interesting to be able to use a resource type as a flow input.
Use case: Define a payload contract between an external system and Windmill to optimize the reuse of input payloads.
The text was updated successfully, but these errors were encountered:
I have the same use case
Sorry, something went wrong.
I'm not sure to follow, would you have a concrete example?
In the current version, to define the input of a flow, we have to copy and paste the JSON payload for each flow.
Proposal: Define it once as a resource type and reuse it as input in other flows.
Got it, it's an interesting idea, thanks for the suggestion
rubenfiszel
No branches or pull requests
It would be interesting to be able to use a resource type as a flow input.
Use case: Define a payload contract between an external system and Windmill to optimize the reuse of input payloads.
The text was updated successfully, but these errors were encountered: