zeebe-modeler
zeebe-modeler copied to clipboard
Profiles for Camunda Cloud / Zeebe Deployment
Is your feature request related to a problem? Please describe.
I am always frustrated when I need to copy credentials from camunda cloud clusters to the Zeebe Modeler for each model.
Describe the solution you'd like
If I have multiple models, I would love to define my cluster credentials once (Camunda Cloud Profile/Accounts), probably using the Copy button in Camunda Cloud and then pasting them into a form and not copying each value for each model.
Describe alternatives you've considered
It will be great if you can choose which profile/account to use when deploying or starting the models.
Additional context
Feature to be considered in this screen.
![Screenshot 2020-09-28 at 17 21 31](https://user-images.githubusercontent.com/271966/94459325-15b4b100-01af-11eb-954e-db17deca2089.png)
Depends on https://github.com/camunda/camunda-modeler/issues/804
Related to https://github.com/zeebe-io/zeebe-modeler/issues/227
Saving credentials for multiple deployments would definitely be a very good improvement.
Also, related to https://github.com/zeebe-io/zeebe-modeler/issues/227
Also notice that currently the credentials are lost when switching diagrams. Profiles would also solve that.
Also notice that currently the credentials are lost when switching diagrams.
What exactly do you mean by being lost?
Regarding this one I think we already have a working pattern in the Camunda Modeler that we should adopt, independent of profiles and stuff.
@salaboy Can you verify what you request is similar to https://github.com/camunda/camunda-modeler/issues/804?
@nikku totally, same use case, but with different information. Notice that there is an issue in Zeebe as well regarding the data format that can be used to store this information (server URL, user, password or credential tokens). https://github.com/zeebe-io/zeebe/issues/3544 In my opinion, in order to define the modeller side, this needs to be solved first on Zeebe and unified with the Camunda BPM engine to follow the same approach, if not we will end up with different ways of configuring things and storing that configuration.
Thanks for the confirmation.