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

Backport 301 to stable/8.0 #312

Merged
merged 8 commits into from
Apr 12, 2022
Merged

Conversation

remcowesterhoud
Copy link
Contributor

Backport #301 to stable 8.0

This test checks if all the gateway endpoints are implemented. Since gRPC does not provide an interface which can force this during compile time we are at risk that updating the Zeebe version could result in ZPT not supporting all endpoints that can be triggered from the client. To circumvent this problem this test was created to make sure we implement all the methods gRPC expects us to.

(cherry picked from commit 3b76c46)
(cherry picked from commit f8c31c6)
The response mapping has been moved from the GrpcResponseWriter to the GrpcToLogStreamGateway. The writer still contains the mapping functions, but they are called from the gateway.

This change is necessary in order to support both the DeployProcessCommand as the DeployResourceCommand. In the writer we don't have any context about the request available. Therefore it is unknown which request we received, and also which response we should return. The mapping was based on the ValueType of the record which is the same for both of these commands.

By letting the gateway decide which mapper should be used this problem has been resolved. At the point of entry of the request we will also decide which mapper should be used for the response. We nog longer need to decide the mapper base on the ValueType.

(cherry picked from commit 5a8d1a7)
DeployProcessCommand is deprecated since Zeebe 8.0.0. In return a new command has been added to the client: DeployResourceCommand. This commit makes it possible to receive this command and return the appropriate response.

(cherry picked from commit 2900923)
DeployCommand has been deprecated since Zeebe 8.0.0. We should use the new DeployResourceCommand as an alternative.

(cherry picked from commit 66f6f49)
(cherry picked from commit ea3ef91)
Copy link
Member

@korthout korthout left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice! LGTM 👍

@github-actions
Copy link

Unit Test Results

   140 files     140 suites   6m 30s ⏱️
   262 tests    262 ✔️ 0 💤 0
1 004 runs  1 004 ✔️ 0 💤 0

Results for commit 5a69ee1.

@remcowesterhoud remcowesterhoud merged commit 51f10d6 into stable/8.0 Apr 12, 2022
@remcowesterhoud remcowesterhoud deleted the backport-301-to-stable/8.0 branch April 12, 2022 14:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants