Skip to content
New issue

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

Allow to propagate a response from the caller back into an input binding #2628

Closed
akkie opened this issue Jan 5, 2021 · 5 comments · Fixed by #2949
Closed

Allow to propagate a response from the caller back into an input binding #2628

akkie opened this issue Jan 5, 2021 · 5 comments · Fixed by #2949
Assignees
Milestone

Comments

@akkie
Copy link
Contributor

akkie commented Jan 5, 2021

In what area(s)?

/area runtime

/area operator
/area placement
/area docs
/area test-and-release

Describe the feature

I try to implement a new input binding for the Zeebe workflow engine. For this I need to acknowledge the binding with a result (process variables) that I then send back to Zeebe to complete the job. Based on the documentation it's possible to acknowledge with a 200 status code but without a response body. There should be a way to propagate a response from the caller back into an input binding.

Release Note

RELEASE NOTE: ADD Support response propagation for input bindings

@akkie
Copy link
Contributor Author

akkie commented Jan 5, 2021

@yaron2 FYI

@yaron2
Copy link
Member

yaron2 commented Jan 5, 2021

Thanks, taking a look at this.

@KaiWalter
Copy link
Contributor

@yaron2 please add it to our project, thanks --- @akkie is on our team

@akkie
Copy link
Contributor Author

akkie commented Mar 2, 2021

Hi @yaron2, any news to this topic?

@yaron2 yaron2 added this to the v1.1 milestone Mar 2, 2021
@yaron2
Copy link
Member

yaron2 commented Mar 2, 2021

Hi @yaron2, any news to this topic?

I triaged it to the 1.1 milestone.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants