[
https://issues.jboss.org/browse/JBIDE-23660?page=com.atlassian.jira.plugi...
]
Ricardo Martinelli Oliveira commented on JBIDE-23660:
-----------------------------------------------------
No matter if it uses 'vagrant destroy' or 'vagrant halt', I still think
that this should be configured in the server adapter. That way the user can choose whether
it's the best for their needs.
If we let the user configure startup options, why not let the users configure stop
options?
CDK Server adapter should have an option to configure stop command
------------------------------------------------------------------
Key: JBIDE-23660
URL:
https://issues.jboss.org/browse/JBIDE-23660
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: cdk
Affects Versions: 4.4.2.Final
Reporter: Ricardo Martinelli Oliveira
Assignee: Rob Stryker
CDK Server adapter lets configure the vagrant startup options. There should have an
option to do the same in the stop.
Why?
It seems that CDK Server adapter uses _vagrant destroy_ to stop CDK, but using that
option has its drawbacks, like for example:
* If I'm stopping it to save resources, then I'm loosing all my job in it.
* All images already pulled will be lost, so I cannot work offline
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)