Handle Endpoint Configuration the same way as in Camunda Modeler

[pinussilvestrus]

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

In every tab, we use the same stored endpoint configuration. Note in the following screencast how the same configuration is filled into the modal, no matter what file we have opened.

We store a single endpoint configuration currently:

 "DEPLOYMENT_CONFIG": {
    "audience": "",
    "camundaCloudClientId": "dump",
    "camundaCloudClientSecret": "dump",
    "camundaCloudClusterId": "dump",
    "connectionMethod": "camundaCloud",
    "deploymentName": "simple",
    "oauthClientId": "",
    "oauthClientSecret": "",
    "oauthURL": "",
    "rememberCredentials": true,
    "zeebeContactPointOauth": "",
    "zeebeContactpointSelfHosted": "0.0.0.0:26500"
 }

This does not match with the behavior we have in the Camunda Modeler, where we

• Diagram specification (deployment name) is saved per file
• Endpoint configuration is saved globally and referenced per file

Describe the solution you'd like

Align endpoint configuration persistence behavior with Camunda Modeler (details above).

Additional Context

Example Config how we have in the Camunda Modeler:

{
  // ...
  "camundaEngineEndpoints": [
    {
      "authType": "bearer",
      "id": "0u3yvpk",
      "rememberCredentials": true,
      "token": "test",
      "url": "http://localhost:8080/rest"
    }
  ],
  "files": {
    "~/BPMN files/diagram_1.bpmn": {
      "deployment-tool": {
        "deployment": {
          "name": "diagram_1"
        },
        "endpointId": "0u3yvpk"
      }
    }
  }
}

[pinussilvestrus]

Okay, removing the local config.json resolved it 🤦🏻‍♂️ Anyway, I'll add a test case to verify it's working at all.

[pinussilvestrus]

@oguzeroglu I was able to reproduce it again. Seems like we're not saving the configuration for each file. This is a part of the config.json

 "DEPLOYMENT_CONFIG": {
    "audience": "",
    "camundaCloudClientId": "DCLBoZVGwNiVmrZBb4ELTrMR1AJtvlBx",
    "camundaCloudClientSecret": "bQE9RDrmUvKKhoCHc7LMenE5WIjvbrE6IIwVdNEkpwywOk3HRKtXS7W65jVxxNWf",
    "camundaCloudClusterId": "d5fd3b34-f3b0-4faa-8e2f-ff57b9358a2b",
    "connectionMethod": "camundaCloud",
    "deploymentName": "complex",
    "oauthClientId": "",
    "oauthClientSecret": "",
    "oauthURL": "",
    "rememberCredentials": true,
    "zeebeContactPointOauth": "",
    "zeebeContactpointSelfHosted": "0.0.0.0:26500"
  }

And therefore this config is used for any tab. Is this intended? In Camunda Modeler we save deployment details for any file separately:

"files": {
    "/Users/niklas.kiefer/Documents/BPMN files/diagram_1.bpmn": {
      "deployment-tool": {
        "deployment": {
          "name": "diagram_1"
        },
        "endpointId": "0u3yvpk"
      },
}

But saving endpoints in a different place so we might be able to have configurable, multiple endpoints in the future.

[barmac]

I would expect the last saved endpoint to be a default for a new diagram, but the deployment name should always be set per file only. Also, if I use a different endpoint configurations for different files, the editor should not mix them up.

[nikku]

We should align this with the Camunda Modeler behavior.

[pinussilvestrus]

I updated the description to match what we discussed.

[barmac]

Closed via #197