Allow to deploy a diagram to a different Camunda Cloud region

Is your feature request related to a problem? Please describe.

With Camunda Cloud 1.1 we added a region to the URL of a Zeebe cluster to be able to route traffic to different regions. You can read a bit about it in the docs https://docs.camunda.io/docs/guides/update-guide/100-to-110#zeebe-java-client.

At the moment for all >= 1.0 clusters in Camunda Cloud only a single default region exists. But in the future we might add more, i.e. we plan to offer a new North America region in the near future.

The user has to be able to specify the region in some way to be able to deploy the diagram to a different region.

A workaround exists by using the Camunda Cloud Self Managed Oauth configuration in the deploy dialog.

Describe the solution you’d like

• Instead of using the Cluster ID, identify the cluster via the Cluster URL.
• Migrate existing configurations (that provided the Cluster ID only) to use bru-2 (cf. https://github.com/camunda/camunda-modeler/issues/2375#issuecomment-889830410) as a region.
• Upon save or deploy persist the Cluster URL in the deployment profile

---

Context and Prior Discussion

@menski At the moment we offer three configuration fields in the deploy dialog, Cluster ID, Client ID and Client Secret.

I see two options but maybe there is another better one:

1. We add a fourth field Region to allow the user to specify the region
2. We replace the Cluster ID field by Cluster URL to allow users to enter the full URL including the region

In my opinion I would prefer option 2 as it is simpler for the user if we enable them to copy the whole address the same way they can copy the client id/secret. In Option 1 they have to copy to information which are always related and will never change separately.

[menski]

that is done in the cloud console, too

Right now the user is seeing the following modal when creating a secret

Which we can easily extend to feature the Cluster URL additionally, which then matches the input fields of the modeler

If we decide to go for this in the modeler then I would make sure that the console will present the cluster URL prominent to the user, and also that the Java and Nodejs client can work with it.

we can introduce that in a backwards compatible manner (i.e. we pick up the currently configured cluster IDs and generate cluster URLs from these, for all cloud >= 1.0 versions)

All saved credentials can only refer to the current defaut bru-2 region, therefore I think it is save to generate the URL out of the saved cluster id on migration.

[menski]

No let me create an issue in console to get that fixed