:construction: This issue is WIP :construction:
__Is your feature request related to a problem? Please describe.__
Context
At the moment the Camunda Cloud infrastructure is creating a DNS entry in the format ${UUID}.zeebe.camunda.io for every Zeebe cluster. This is the unique address the cluster is available at for the user to connect to.
Solution approach by the cloud team: use a single DNS address per region and provide cluster UUID using the :authority pseudo header.
What this means for us
(As of now) the assumption is that zeebe-node-js will be released in a new version which supports zeebe 1.0 and zeebe 1.1.
Based on that assumption, we would need to update to that latest version and ensure everything still works as expected.
__Describe alternatives you've considered__
Integrate two versions of zeebe-node-js (We can not do that)
__Additional context__
RfC: https://docs.google.com/document/d/1FvTVcSFLactlF0Mw1npq19O-iir4QHzNpzIj4Fzk9S0/edit#
cc @barmac
Did we receive an update from upstream regarding when and if that thing is going to be delivered? Asking as the release manager for the upcoming release.
@jwulf is working on a new version of zeebe-node which should support Zeebe 1.1 without any API changes. We will get a status update on Monday.
Since [email protected] is out, we can test that.
Most helpful comment
@jwulf is working on a new version of
zeebe-nodewhich should support Zeebe 1.1 without any API changes. We will get a status update on Monday.