Migrate from zeebe-node to @camunda8/sdk

[abdul99ahad]

Closes #4109

Proposed Changes

Migrated client from zeebe-node (deprecated) to camunda8-sdk

How to test

Camnda 8 SaaS

Docs: https://docs.camunda.io/docs/components/modeler/desktop-modeler/connect-to-camunda-8/

Camunda 8 Self-Managed

Authentication: None

Checkout https://github.com/camunda/zeebe-connection-test. Here you can spin up the docker environment with environment variables and certificates to test the connection

Insecure Connection (without SSL)

# (once) ensure the configured hostname resolves to 127.0.0.1
ZEEBE_HOSTNAME=sub.example.com sh -c 'echo "127.0.0.1    $ZEEBE_HOSTNAME"' | sudo tee -a /etc/hosts

ZEEBE_HOSTNAME=sub.example.com docker compose --env-file .env.insecure up

Secure Connection (with SSL)

# (once) ensure the configured hostname resolves to 127.0.0.1
ZEEBE_HOSTNAME=sub.example.com sh -c 'echo "127.0.0.1    $ZEEBE_HOSTNAME"' | sudo tee -a /etc/hosts

# start zeebe with security enabled
ZEEBE_HOSTNAME=sub.example.com docker compose up zeebe

To test with the Camunda Modeler pass the custom SSL root certificate use the --zeebe-ssl-certificate flag:

camunda-modeler --zeebe-ssl-certificate=cert/root.crt

Authentication: Basic

Checkout this branch #basic-auth (https://github.com/camunda/zeebe-connection-test/tree/basic-auth)
For this to test, create a secure connection via reverse proxy
creds: demo:demo
port: 8181

# (once) ensure the configured hostname resolves to 127.0.0.1
ZEEBE_HOSTNAME=sub.example.com sh -c 'echo "127.0.0.1    $ZEEBE_HOSTNAME"' | sudo tee -a /etc/hosts

# start zeebe with security enabled
ZEEBE_HOSTNAME=sub.example.com docker compose --env-file .env.proxy up zeebe proxy

source: https://github.com/camunda/zeebe-connection-test/blob/basic-auth/README.md

Authentication: OAuth

Same as Camunda SAAS, just select Camunda self managed with OAuth

Tip

TL;DR: You can use zeebe-connection-test to test the sdk.

Checklist

To ensure you provided everything we need to look at your PR:

• Brief textual description of the changes present
• Visual demo attached
• Steps to try out present, i.e. using the @bpmn-io/sr tool
• Related issue linked via Closes {LINK_TO_ISSUE} or Related to {LINK_TO_ISSUE}

[github-actions]

This Pull Request targets develop branch, but contains fix commits.

Consider targeting main instead.

[philippfromme]

Let's not duplicate this helper and maybe also make it a bit more forgiving:

function removeProtocol(url) {
  const urlObject = new URL(url);
  return urlObject.host + urlObject.pathname;
}

[philippfromme]

I'd say let's not add the URL minus the protocol everywhere. We have the full URL anyway and we can remove the protocol when creating the Zeebe GRPC client.

[philippfromme]

Let's rename this configuration for clarity to something like zeebeGrpcApiClient which is what this configuration is for.

[philippfromme]

Again, this commit changes tests only. It's much easier for the reviewer if changes and the respective tests are bundled together.