zeebe-client 0.11.0 → 0.11.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 8c458c30ca89e870cabbead8c0672fdebe62969e28cdf031f64675240eddcb45
-  data.tar.gz: 8c51e32007c3a18bd5adc20d52c6b0d26ae6068866684dec7c809202a92f65e8
+  metadata.gz: 0b9b6cf4bb5477d80cfd94fda6fa7d6723c49216438e648c9b363f969fc91799
+  data.tar.gz: e42b10ea9c670af9b9b11831bd05ab1f6a0631a759be039f68282c8e7e912d71
 SHA512:
-  metadata.gz: 57cfbc109cc7624026c0a25b1ed7bd87281e6ee04d3f79b591a870715606d5c47c385eba2de63c9a8b6961cd75b1f0255cd622f3c634ff877f5626cd75638947
-  data.tar.gz: 43aa739e75b8bd6123503e464f376f46569fb414ccdc472c04403eb0d535ad102b62ac20075cd38a865861f733e70c2df6d1216a17ed4cb6fe95a4213abb0256
+  metadata.gz: 235f9c662230f0185a7b3ccc8f0d73d1b59a2fdb21fa19297c9f68dd222a78fc9fe03e3943c2cd28092c9bd54417dcfc6f8c885b53210b761e9ef83419205649
+  data.tar.gz: bc0520f417c70ee70949ddc43baed4ea3e02661b12aa829ccd08839e82bbae74e018367813cd03cfa1db55d381784c1bb11da404d3c35e3b567f5a608c721318

data/CHANGELOG.md

@@ -1,5 +1,9 @@
 # Changelog
 
+## 0.11.1 (November 4, 2020)
+
+- add support for [Zeebe 0.24.3](https://github.com/zeebe-io/zeebe/releases/tag/0.24.3)
+
 ## 0.11.0 (July 29, 2020)
 
 - support Ruby 2.7

data/README.md

@@ -13,7 +13,7 @@ Install the gem:
 Run a Zeebe instance locally:
 
 ```sh
-docker run -it --rm -p 26500:26500 camunda/zeebe:0.24.1
+docker run -it --rm -p 26500:26500 camunda/zeebe:0.24.3
 ```
 
 And then try the available [demo script](examples/demo.rb).

data/Rakefile

@@ -13,7 +13,7 @@ task travis: ['zeebe:start', :default, 'zeebe:stop']
 
 desc 'Starts Zeebe Docker container'
 task 'zeebe:start' do
-  sh 'docker run -d --name zeebe --rm -p 26500:26500 camunda/zeebe:0.24.1'
+  sh 'docker run -d --name zeebe --rm -p 26500:26500 camunda/zeebe:0.24.3'
   sleep(10)
 end
 

data/examples/demo.rb

@@ -13,8 +13,3 @@ puts "  Brokers:"
 topology.brokers.each do |b|
   puts "    - id: #{b.nodeId}, address: #{b.host}:#{b.port}, partitions: #{b.partitions.map { |p| p.partitionId }}"
 end
-
-workflows = zeebe_client.list_workflows(Zeebe::Client::GatewayProtocol::ListWorkflowsRequest.new).workflows
-
-puts ""
-puts "Zeebe workflows: #{workflows.inspect}"

data/gen-grpc.sh

@@ -6,5 +6,5 @@ genPath="lib/zeebe/client"
 grpc_tools_ruby_protoc "${protoPath}/gateway.proto" --ruby_out="${genPath}" --grpc_out="${genPath}"
 
 sed -i 's@proto/gateway_pb@zeebe/client/proto/gateway_pb@g' "${genPath}/proto/gateway_services_pb.rb"
-sed -i 's@module GatewayProtocol@module Zeebe::Client::GatewayProtocol@g' "${genPath}/proto/gateway_pb.rb"
-sed -i 's@module GatewayProtocol@module Zeebe::Client::GatewayProtocol@g' "${genPath}/proto/gateway_services_pb.rb"
+sed -i 's@GatewayProtocol@Zeebe::Client::GatewayProtocol@g' "${genPath}/proto/gateway_pb.rb"
+sed -i 's@GatewayProtocol@Zeebe::Client::GatewayProtocol@g' "${genPath}/proto/gateway_services_pb.rb"

data/lib/zeebe/client/proto/gateway_services_pb.rb

@@ -24,14 +24,14 @@ module Zeebe::Client::GatewayProtocol
       # - worker is blank (empty string, null)
       # - timeout less than 1
       # - maxJobsToActivate is less than 1
-      rpc :ActivateJobs, ActivateJobsRequest, stream(ActivateJobsResponse)
+      rpc :ActivateJobs, ::Zeebe::Client::GatewayProtocol::ActivateJobsRequest, stream(::Zeebe::Client::GatewayProtocol::ActivateJobsResponse)
       #
       # Cancels a running workflow instance
       #
       # Errors:
       # NOT_FOUND:
       # - no workflow instance exists with the given key
-      rpc :CancelWorkflowInstance, CancelWorkflowInstanceRequest, CancelWorkflowInstanceResponse
+      rpc :CancelWorkflowInstance, ::Zeebe::Client::GatewayProtocol::CancelWorkflowInstanceRequest, ::Zeebe::Client::GatewayProtocol::CancelWorkflowInstanceResponse
       #
       # Completes a job with the given variables, which allows completing the associated service task.
       #
@@ -43,7 +43,7 @@ module Zeebe::Client::GatewayProtocol
       # FAILED_PRECONDITION:
       # - the job was marked as failed. In that case, the related incident must be resolved before
       # the job can be activated again and completed.
-      rpc :CompleteJob, CompleteJobRequest, CompleteJobResponse
+      rpc :CompleteJob, ::Zeebe::Client::GatewayProtocol::CompleteJobRequest, ::Zeebe::Client::GatewayProtocol::CompleteJobResponse
       #
       # Creates and starts an instance of the specified workflow. The workflow definition to use to
       # create the instance can be specified either using its unique key (as returned by
@@ -64,10 +64,10 @@ module Zeebe::Client::GatewayProtocol
       # INVALID_ARGUMENT:
       # - the given variables argument is not a valid JSON document; it is expected to be a valid
       # JSON document where the root node is an object.
-      rpc :CreateWorkflowInstance, CreateWorkflowInstanceRequest, CreateWorkflowInstanceResponse
+      rpc :CreateWorkflowInstance, ::Zeebe::Client::GatewayProtocol::CreateWorkflowInstanceRequest, ::Zeebe::Client::GatewayProtocol::CreateWorkflowInstanceResponse
       #
       # Behaves similarly to `rpc CreateWorkflowInstance`, except that a successful response is received when the workflow completes successfully.
-      rpc :CreateWorkflowInstanceWithResult, CreateWorkflowInstanceWithResultRequest, CreateWorkflowInstanceWithResultResponse
+      rpc :CreateWorkflowInstanceWithResult, ::Zeebe::Client::GatewayProtocol::CreateWorkflowInstanceWithResultRequest, ::Zeebe::Client::GatewayProtocol::CreateWorkflowInstanceWithResultResponse
       #
       # Deploys one or more workflows to Zeebe. Note that this is an atomic call,
       # i.e. either all workflows are deployed, or none of them are.
@@ -79,7 +79,7 @@ module Zeebe::Client::GatewayProtocol
       # - it is not a BPMN or YAML file (currently detected through the file extension)
       # - the resource data is not deserializable (e.g. detected as BPMN, but it's broken XML)
       # - the workflow is invalid (e.g. an event-based gateway has an outgoing sequence flow to a task)
-      rpc :DeployWorkflow, DeployWorkflowRequest, DeployWorkflowResponse
+      rpc :DeployWorkflow, ::Zeebe::Client::GatewayProtocol::DeployWorkflowRequest, ::Zeebe::Client::GatewayProtocol::DeployWorkflowResponse
       #
       # Marks the job as failed; if the retries argument is positive, then the job will be immediately
       # activatable again, and a worker could try again to process it. If it is zero or negative however,
@@ -93,7 +93,7 @@ module Zeebe::Client::GatewayProtocol
       # FAILED_PRECONDITION:
       # - the job was not activated
       # - the job is already in a failed state, i.e. ran out of retries
-      rpc :FailJob, FailJobRequest, FailJobResponse
+      rpc :FailJob, ::Zeebe::Client::GatewayProtocol::FailJobRequest, ::Zeebe::Client::GatewayProtocol::FailJobResponse
       #
       # Reports a business error (i.e. non-technical) that occurs while processing a job. The error is handled in the workflow by an error catch event. If there is no error catch event with the specified errorCode then an incident will be raised instead.
       #
@@ -103,7 +103,7 @@ module Zeebe::Client::GatewayProtocol
       #
       # FAILED_PRECONDITION:
       # - the job is not in an activated state
-      rpc :ThrowError, ThrowErrorRequest, ThrowErrorResponse
+      rpc :ThrowError, ::Zeebe::Client::GatewayProtocol::ThrowErrorRequest, ::Zeebe::Client::GatewayProtocol::ThrowErrorResponse
       #
       # Publishes a single message. Messages are published to specific partitions computed from their
       # correlation keys.
@@ -111,7 +111,7 @@ module Zeebe::Client::GatewayProtocol
       # Errors:
       # ALREADY_EXISTS:
       # - a message with the same ID was previously published (and is still alive)
-      rpc :PublishMessage, PublishMessageRequest, PublishMessageResponse
+      rpc :PublishMessage, ::Zeebe::Client::GatewayProtocol::PublishMessageRequest, ::Zeebe::Client::GatewayProtocol::PublishMessageResponse
       #
       # Resolves a given incident. This simply marks the incident as resolved; most likely a call to
       # UpdateJobRetries or SetVariables will be necessary to actually resolve the
@@ -120,7 +120,7 @@ module Zeebe::Client::GatewayProtocol
       # Errors:
       # NOT_FOUND:
       # - no incident with the given key exists
-      rpc :ResolveIncident, ResolveIncidentRequest, ResolveIncidentResponse
+      rpc :ResolveIncident, ::Zeebe::Client::GatewayProtocol::ResolveIncidentRequest, ::Zeebe::Client::GatewayProtocol::ResolveIncidentResponse
       #
       # Updates all the variables of a particular scope (e.g. workflow instance, flow element instance)
       # from the given JSON document.
@@ -131,10 +131,10 @@ module Zeebe::Client::GatewayProtocol
       # INVALID_ARGUMENT:
       # - the given variables document is not a valid JSON document; valid documents are expected to
       # be JSON documents where the root node is an object.
-      rpc :SetVariables, SetVariablesRequest, SetVariablesResponse
+      rpc :SetVariables, ::Zeebe::Client::GatewayProtocol::SetVariablesRequest, ::Zeebe::Client::GatewayProtocol::SetVariablesResponse
       #
       # Obtains the current topology of the cluster the gateway is part of.
-      rpc :Topology, TopologyRequest, TopologyResponse
+      rpc :Topology, ::Zeebe::Client::GatewayProtocol::TopologyRequest, ::Zeebe::Client::GatewayProtocol::TopologyResponse
       #
       # Updates the number of retries a job has left. This is mostly useful for jobs that have run out of
       # retries, should the underlying problem be solved.
@@ -145,7 +145,7 @@ module Zeebe::Client::GatewayProtocol
       #
       # INVALID_ARGUMENT:
       # - retries is not greater than 0
-      rpc :UpdateJobRetries, UpdateJobRetriesRequest, UpdateJobRetriesResponse
+      rpc :UpdateJobRetries, ::Zeebe::Client::GatewayProtocol::UpdateJobRetriesRequest, ::Zeebe::Client::GatewayProtocol::UpdateJobRetriesResponse
     end
 
     Stub = Service.rpc_stub_class

data/lib/zeebe/client/version.rb

@@ -1,6 +1,6 @@
 
 module Zeebe
   module Client
-    VERSION = '0.11.0'.freeze
+    VERSION = '0.11.1'.freeze
   end
 end

data/zeebe-client.gemspec

@@ -19,11 +19,11 @@ Gem::Specification.new do |s|
 
   s.required_ruby_version = '>= 2.3'
 
-  s.add_runtime_dependency 'grpc', '~> 1.28.0'
+  s.add_runtime_dependency 'grpc', '~> 1.32.0'
 
   s.add_development_dependency 'bundler'
   s.add_development_dependency 'bundler-audit', '~> 0.7.0'
-  s.add_development_dependency 'grpc-tools', '~> 1.28.0'
+  s.add_development_dependency 'grpc-tools', '~> 1.32.0'
   s.add_development_dependency 'rake'
   s.add_development_dependency 'rspec'
   s.add_development_dependency 'rubocop', '~> 0.81.0'

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: zeebe-client
 version: !ruby/object:Gem::Version
-  version: 0.11.0
+  version: 0.11.1
 platform: ruby
 authors:
 - Christian Nicolai
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2020-07-29 00:00:00.000000000 Z
+date: 2020-11-04 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: grpc
@@ -16,14 +16,14 @@ dependencies:
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 1.28.0
+        version: 1.32.0
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 1.28.0
+        version: 1.32.0
 - !ruby/object:Gem::Dependency
   name: bundler
   requirement: !ruby/object:Gem::Requirement
@@ -58,14 +58,14 @@ dependencies:
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 1.28.0
+        version: 1.32.0
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 1.28.0
+        version: 1.32.0
 - !ruby/object:Gem::Dependency
   name: rake
   requirement: !ruby/object:Gem::Requirement
@@ -169,7 +169,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.0.8
+rubygems_version: 3.1.4
 signing_key: 
 specification_version: 4
 summary: Zeebe Client