Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Be able to create re-usable deploy configurations #804

Open
yanavasileva opened this issue May 14, 2018 · 5 comments
Open

Be able to create re-usable deploy configurations #804

yanavasileva opened this issue May 14, 2018 · 5 comments
Labels
backlog Queued in backlog Camunda 7 Flags an issue as related to Camunda Automation Platform 7 Camunda 8 Flags an issue as related to Camunda 8 deploy enhancement New feature or request

Comments

@yanavasileva
Copy link
Member

yanavasileva commented May 14, 2018 •
edited by nikku
Loading

Describe the problem

As a user of the Modeler I have different tasks which require different connections to the Camunda world, i.e. I use a number of different connections for local testing, staged testing, and (though very unlikely) prod deployment.

Right now I have to change the existing deployment configuration every time. What I want instead is to be able to simply select a previously configured connection, and use it during deployment.

Describe the solution

I want to setup two different endpoints with separate credentials for the both of the engines, i.e.

http://localhost:8080/engine-rest/deployment/create
http://192.168.178.107:7001/camunda/engine-rest/deployment/create

I don't need to edit the endpoint on each deploy when switching the engine.
(Maybe I can only select already saved engines from dropdown menu or something like this?)

Related to #1439.

See also UI sketches for details on the complete picture.

Related to #4692 (complex configurations would massively benefit from this).
@nikku nikku added backlog Queued in backlog deploy labels May 14, 2018
@nikku
Copy link
Member

nikku commented May 14, 2018

Makes a lot of sense and fits very well in the general deploy improvements bucket.

@nikku nikku added the enhancement New feature or request label May 14, 2018
@philippfromme philippfromme mentioned this issue Nov 20, 2018
Closed
6 tasks
@nikku nikku added ready Ready to be worked on and removed backlog Queued in backlog labels Nov 23, 2018
@nikku nikku added this to the M26 milestone Nov 23, 2018
@philippfromme philippfromme mentioned this issue Dec 11, 2018
Closed
58 tasks
@nikku nikku mentioned this issue Jan 17, 2019
Closed
25 tasks
@nikku nikku modified the milestones: M26, M27 Jan 17, 2019
@nikku nikku removed this from the M27 milestone Feb 7, 2019
@nikku nikku added backlog Queued in backlog and removed ready Ready to be worked on labels Feb 12, 2019
@yanavasileva
Copy link
Member Author

Hi @nikku,

I want to bring this topic again to your attention.
Having such feature will help us during testing.
Is there any chance to reconsider it for some of the next Modeler releases?

Best,
Yana

@nikku nikku added the PM label Jun 2, 2019
@nikku
Copy link
Member

nikku commented Jun 2, 2019

We will reconsider this feature request in our next planning session.

@nikku nikku added ready Ready to be worked on and removed PM backlog Queued in backlog labels Jul 8, 2019
@nikku nikku added this to the M30 milestone Jul 8, 2019
@bpmn-io-tasks bpmn-io-tasks bot added in progress Currently worked on and removed ready Ready to be worked on labels Jul 23, 2019
@barmac
Copy link
Collaborator

barmac commented Jul 24, 2019

Idea: have a separate place where you can configure and save the endpoints with/without credentials; allow to choose which servers deploy to and remember this config.

@nikku nikku mentioned this issue Jul 24, 2019
Closed
1 task
@barmac barmac mentioned this issue Jul 24, 2019
Closed
9 tasks
@barmac barmac removed the in progress Currently worked on label Jul 26, 2019 — with bpmn-io-tasks
@barmac barmac added the ready Ready to be worked on label Jul 26, 2019 — with bpmn-io-tasks
@nikku nikku modified the milestones: M30, M31 Aug 12, 2019
@volkergersabeck volkergersabeck removed this from the M31 milestone Sep 24, 2019
@volkergersabeck
Copy link

Unfortunately, we weren't able to tackle this topic in the current quarter and will also not focus on it in the next quarter due to other priorities.

@volkergersabeck volkergersabeck added backlog Queued in backlog and removed ready Ready to be worked on labels Sep 24, 2019 — with bpmn-io-tasks
@barmac barmac removed their assignment Oct 22, 2019
nikku added a commit that referenced this issue Nov 22, 2019
@nikku
feat(deploy): remember authentication details
fe793cd 
* remember authentication details, if the user actively
  decides this
* restore global endpoint configuration, as intended until
  it is properly addressed via #804
* refactor deployment tool, pulling out validation into separate
  component
* pull out menu update functionality to be re-added at a later
  point in time, in a different place
* deployment tool UI remains untouched

Closes #1067
nikku added a commit that referenced this issue Nov 22, 2019
@nikku
feat(deploy): remember authentication details
85faa85 
* remember authentication details, if the user actively
  decides this
* restore global endpoint configuration, as intended until
  it is properly addressed via #804
* refactor deployment tool, pulling out validation into separate
  component
* pull out menu update functionality to be re-added at a later
  point in time, in a different place
* deployment tool UI remains untouched

Closes #1067
nikku added a commit that referenced this issue Nov 22, 2019
@nikku
feat(deploy): remember authentication details
1a22068 
* remember authentication details, if the user actively
  decides this
* restore global endpoint configuration, as intended until
  it is properly addressed via #804
* refactor deployment tool, pulling out validation into separate
  component
* pull out menu update functionality to be re-added at a later
  point in time, in a different place
* deployment tool UI remains untouched

Closes #1067
nikku added a commit that referenced this issue Nov 22, 2019
@nikku
feat(deploy): remember authentication details
5334c8a 
* remember authentication details, if the user actively
  decides this
* restore global endpoint configuration, as intended until
  it is properly addressed via #804
* refactor deployment tool, pulling out validation into separate
  component
* pull out menu update functionality to be re-added at a later
  point in time, in a different place
* deployment tool UI remains untouched

Closes #1067
pinussilvestrus pushed a commit that referenced this issue Nov 22, 2019
@nikku
feat(deploy): remember authentication details
eb35b07 
* remember authentication details, if the user actively
  decides this
* restore global endpoint configuration, as intended until
  it is properly addressed via #804
* refactor deployment tool, pulling out validation into separate
  component
* pull out menu update functionality to be re-added at a later
  point in time, in a different place
* deployment tool UI remains untouched

Closes #1067
@nikku nikku mentioned this issue Nov 13, 2020
Open
@nikku nikku changed the title I can setup and use more than one endpoint when deploying Be able to create re-usable deploy configurations Oct 31, 2024
@nikku nikku added Camunda 7 Flags an issue as related to Camunda Automation Platform 7 Camunda 8 Flags an issue as related to Camunda 8 labels Oct 31, 2024
This was referenced Nov 14, 2024
Open
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
backlog Queued in backlog Camunda 7 Flags an issue as related to Camunda Automation Platform 7 Camunda 8 Flags an issue as related to Camunda 8 deploy enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@nikku @volkergersabeck @yanavasileva @barmac