Update 0.26 to 1.0
Please be aware that the major version update from 0.26 to 1.0 is not backwards compatible. Therefore data cannot be migrated from 0.26 to 1.0 and client applications have to be adjusted to the new API versions.
The following sections will explain for each component of the system which adjustments have to be made to migrate from Camunda Cloud 0.26.x to 1.0.0
Server​
Zeebe​
Distribution​
With Zeebe 1.0.0 the Java package names where adjusted. They changed from
io.zeebe to io.camunda.zeebe. Therefore any logging configurations and
similar, which are based on the package names have to be adjusted.
Additionally the group id of the Java artifacts where migrated from io.zeebe
to io.camunda. Which requires all dependencies to the artifacts to be updated
to use the new group id.
The downloadable artifact of the Zeebe distribution was renamed from
zeebe-distribution-${VERSION}.tar.gztocamunda-cloud-zeebe-${VERSION}.tar.gz,zeebe-distribution-${VERSION}.ziptocamunda-cloud-zeebe-${VERSION}.zip
Workflow Engine​
The support for YAML workflows was removed from the workflow engine, after the deprecation with 0.26. Meaning only BPMN processes are support from now on.
Elasticsearch Exporter​
The supported Elasticsearch version of the Elasticsearch Exporter was increased
from 6.8 to 7.10, read more about this in the
Elasticsearch section.
The index templates of the Elasticsearch Exporter were migrated to use composable index templates.
Protocol​
The Java protocol received the following adjustments:
Enum
IncidentIntent- remove
CREATE - change short value of
CREATEDto0 - change short value of
RESOLVEto1 - change short value of
RESOLVEDto2
- remove
Enum
WorkflowInstanceIntentrenamed toProcessInstanceIntentEnum
WorkflowInstanceSubscriptionIntentrenamed toProcessMessageSubscriptionIntentEnum
WorkflowInstanceCreationIntentrenamed toProcessInstanceCreationIntentEnum
JobIntent- remove
CREATEandACTIVATED - change short value of
CREATEDto0 - change short value of
COMPLETEto1 - change short value of
COMPLETEDto2 - change short value of
TIME_OUTto3 - change short value of
TIMED_OUTto4 - change short value of
FAILto5 - change short value of
FAILEDto6 - change short value of
UPDATE_RETRIESto7 - change short value of
RETRIES_UPDATEDto8 - change short value of
CANCELto9 - change short value of
CANCELEDto10 - change short value of
THROW_ERRORto11 - change short value of
ERROR_THROWNto12
- remove
Enum
MessageIntent- rename
DELETEtoEXPIRE - rename
DELETEDtoEXPIRED
- rename
Enum
MessageStartEventSubscriptionIntent- remove
OPEN,OPENED,CLOSEandCLOSED - add
CREATED,CORRELATEDandDELETED
- remove
Enum
MessageSubscriptionIntent- rename
OPENtoCREATE - rename
OPENEDtoCREATED - rename
CLOSEtoDELETE - rename
CLOSEDtoDELETED - add `CORRELATING
- rename
Enum
TimerIntent- remove
CREATE - change short value of
CREATEDto0 - change short value of
TRIGGERto1 - change short value of
TRIGGEREDto2 - change short value of
CANCELto3 - change short value of
CANCELEDto4
- remove
Interface
DeploymentRecordValue- rename method
getDeployedWorkflowstogetProcessMetadataand change type fromList<DeployedWorkflow>toList<ProcessMetadataValue>
- rename method
Interface
IncidentRecordValue- rename method
getWorkflowKeytogetProcessDefinitionKey - rename method
getWorkflowInstanceKeytogetProcessInstanceKey
- rename method
Interface
JobRecordValue- rename method
getWorkflowDefinitionVersiontogetProcessDefinitionVersion - rename method
getWorkflowKeytogetProcessDefinitionKey
- rename method
Interface
MessageStartEventSubscriptionRecordValue- rename method
getWorkflowKeytogetProcessDefinitionKey - rename method
getWorkflowInstanceKeytogetProcessInstanceKey
- rename method
Interface
MessageSubscriptionRecordValue- rename method
getWorkflowInstanceKeytogetProcessInstanceKey
- rename method
Interface
TimerRecordValue- rename method
getWorkflowKeytogetProcessDefinitionKey - rename method
getWorkflowInstanceKeytogetProcessInstanceKey
- rename method
Interface
VariableRecordValue- rename method
getWorkflowInstanceKeytogetProcessInstanceKey - rename method
getWorkflowKeytogetProcessDefinitionKey
- rename method
gRPC​
The following changes were made to the gRPC protocol definition:
ActivatedJobmessage- rename field
workflowInstanceKeytoprocessInstanceKey - rename field
workflowDefinitionVersiontoprocessDefinitionVersion - rename field
workflowKeytoprocessDefinitionKey
- rename field
CancelWorkflowInstanceRequestmessage renamed toCancelProcessInstanceRequest- rename field
workflowInstanceKeytoprocessInstanceKey
- rename field
CancelWorkflowInstanceResponsemessage renamed toCancelProcessInstanceResponseCreateWorkflowInstanceRequestmessage renamed toCreateProcessInstanceRequest- rename field
workflowKeytoprocessDefinitionKey
- rename field
CreateWorkflowInstanceResponsemessage renamed toCreateProcessInstanceResponse- rename field
workflowKeytoprocessDefinitionKey - rename field
workflowInstanceKeytoprocessInstanceKey
- rename field
CreateWorkflowInstanceWithResultRequestmessage renamed toCreateProcessInstanceWithResultRequest- change type of field
requestfromCreateWorkflowInstanceRequesttoCreateProcessInstanceRequest
- change type of field
CreateWorkflowInstanceWithResultResponsemessage renamed toCreateProcessInstanceWithResultResponse- rename field
workflowKeytoprocessDefinitionKey - rename field
workflowInstanceKeytoprocessInstanceKey
- rename field
DeployWorkflowRequestmessage renamed toDeployProcessRequest- rename field
workflowstoprocessesand change type fromWorkflowRequestObjecttoProcessRequestObject
- rename field
WorkflowRequestObjectmessage renamed toProcessRequestObject- remove enum
ResourcetType - remove field type
- change field id of
definitionfield to 2
- remove enum
DeployWorkflowResponsemessage renamed toDeployProcessResponse- rename field
wokrflowstoprocessesand change type fromWorkflowMetadatatoProcessMetadata
- rename field
WorkflowMetadatamessage renamed toProcessMetadata- rename field
workflowKeytoprocessDefinitionKey
- rename field
Partitionmessage- enum
PartitionBrokerRoleaddedINACTIVEstate
- enum
Gatewayservicerename rpc
CancelWorkflowInstancetoCancelProcessInstanceand change input type fromCancelWorkflowInstanceRequesttoCancelProcessInstanceRequestand output type fromCancelWorkflowInstanceResponsetoCancelProcessInstanceResponserename rpc
CreateWorkflowInstancetoCreateProcessInstanceand change input type fromCreateWorkflowInstanceRequesttoCreateProcessInstanceRequestand output type fromCreateWorkflowInstanceResponsetoCreateProcessInstanceResponserename rpc
CreateWorkflowInstanceWithResulttoCreateProcessInstanceand change input type fromCreateWorkflowInstanceWithResultRequesttoCreateProcessInstanceWithResultRequestand output type fromCreateWorkflowInstanceWithResultResponsetoCreateProcessInstanceResponserename rpc
DeployWorkflowtoDeployProcessand change input type fromDeployWorkflowRequesttoDeployProcessRequestand output type fromDeployWorkflowResponsetoDeployProcessResponse
Exporter API​
In the Java Exporter API the depracted method Controller#scheduleTask
removed.
Operate​
With Operate 1.0.0 the Java package names where adjusted. They changed from
org.camunda.operate to io.camunda.operate. Therefore any logging
configurations and similar, which are based on the package names have to be
adjusted.
The downloadable artifact of the Operate distribution was renamed from
camunda-operate-${VERSION}.tar.gztocamunda-cloud-operate-${VERSION}.tar.gz,camunda-operate-${VERSION}.ziptocamunda-cloud-operate-${VERSION}.zip
The supported Elasticsearch version was increased from 6.8 to 7.10, read
more about this in the Elasticsearch section.
Tasklist​
With Tasklist 1.0.0 the Java package names where adjusted. They changed from
io.zeebe.tasklist to io.camunda.tasklist. Therefore any logging
configurations and similar, which are based on the package names have to be
adjusted.
Additionally also the configuration prefix was migrated from zeebe.tasklist to
camunda.tasklist, which requires all configurations to be adjusted to the new
prefix.
The downloadable artifact of the Tasklist distribution was renamed from
zeebe-tasklist-${VERSION}.tar.gztocamunda-cloud-tasklist-${VERSION}.tar.gz,zeebe-tasklist-${VERSION}.ziptocamunda-cloud-tasklist-${VERSION}.zip
The supported Elasticsearch version was increased from 6.8 to 7.10, read
more about this in the Elasticsearch section.
Elasticsearch​
Zeebe, Operate and Tasklist use Elasticsearch as Datastore to exchange the event stream from Zeebes exporter, and store their own data model representation.
Camunda Cloud 1.0 requires an update from Elasticsearch 6.8 to 7.10. Please follow the update guide from Elasticsearch, to migrate existing data. But please note that Zeebe, Operate and Tasklist data inside Elasticsearch cannot be migrated, it can only be preserved for histroy or audit purpose, but cannot be loaded by the Camunda Cloud 1.0.
If you want to keep the existing data in Elasticsearch, please ensure to set a new index prefix for all systems, see the configuration documentation for Zeebe, Operate and Tasklist.
Client​
Zeebe Java Client​
With Zeebe 1.0.0 the Java package names where adjusted. They changed from
io.zeebe to io.camunda.zeebe. Therefore any imports and logging
configurations and similar, which are based on the package names have to be
adjusted.
Additionally the group id of the Java artifacts where migrated from io.zeebe
to io.camunda. Which requires all dependencies to the artifacts to be updated
to use the new group id.
The public API of the Java client changed as follows:
Interface
ActivatedJob- rename method
getWorkflowInstanceKeytogetProcessInstanceKey - rename method
getWorkflowDefinitionVersiontogetProcessDefinitionVersion - rename method
getWorkflowKeytogetProcessDefinitionKey
- rename method
Class
ClientProperties- remove deprecated field
BROKER_CONTACTPOINT
- remove deprecated field
Interface
ZeebeClientBuilder- remove deprecated method
brokerContactPoint
- remove deprecated method
Interface
ZeebeClientConfiguration- remove deprecated method
getBrokerContactPoint
- remove deprecated method
Interface
ZeebeClient- change return type of
newDeployCommandfromDeployWorkflowCommandStep1toDeployProcessCommandStep1 - change return type of
newCreateInstanceCommandfromCreateWorkflowInstanceCommandStep1toCreateProcessInstanceCommandStep1 - change return type of
newCancelInstanceCommandfromCancelWorkflowInstanceCommandStep1toCancelProcessInstanceCommandStep1
- change return type of
Zeebe Go Client​
The repository of Zeebe was moved from github.com/zeebe-io/zeebe to
github.com/camunda-cloud/zeebe, therefore all go dependencies and imports have
to be adjusted to the new github URL.
The public API of the Go client was changed as follows:
Interface
CancelInstanceStep1- rename method
WorkflowInstanceKeytoProcessInstanceKeyand change return type fromDispatchCancelWorkflowInstanceCommandtoDispatchCancelProcessInstanceCommand
- rename method
Interface
DispatchCancelWorkflowInstanceCommandrenamed toDispatchCancelProcessInstanceCommandInterface
CancelWorkflowInstanceCommandrenamed toCancelProcessInstanceCommand- rename method
WorkflowInstanceKeytoProcessInstanceKey
- rename method
Interface
CreateInstanceCommandStep1- rename method
WorkflowKeytoProcessDefinitionKeyand changeDispatchCancelProcessInstanceCommand
- rename method
Struct
DeployCommand- method
AddResource(definition, name, resourceType)removeresourceTypefrom parameter list
- method
Interface
Client- rename method
NewDeployWorkflowCommandtoNewDeployProcessCommand
- rename method