[jbosstools-issues] [JBoss JIRA] (JBIDE-25055) Support the profile feature in CDK server adapter

[Ondrej Dockal (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-25055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13483241#comment-13483241 ] 

Ondrej Dockal commented on JBIDE-25055:
---------------------------------------

Verified on devstudio 11.1.0.GA-v20171026-1022-B1486.

Verification steps: 
Use case 1: CDK 3.2+ Server Adapter can be operated
1. EXEC: There is no old CDK configuration, have CDK with profiles feature downloaded, 'setup-cdk' called - happens out of IDE
2. EXEC: Create New CDK 3.2+ server with default values (profile = minishift)
3. EXEC: Start/Stop/Restart server adapter
4. ASSERT: Check that OS 3 connection was created (SSL Cert. was accepted), Docker connection was created, SA state is started (stopped)

Use case 2: CDK 3.2+ Server Adapter can operate another profile
1. EXEC: There is no old CDK configuration, have CDK with profiles feature downloaded, 'setup-cdk' called - happens out of IDE
2. EXEC: Create New CDK 3.2+ server with profile set to value different than "minishift"
3. EXEC: Start/Stop/Restart server adapter
4. ASSERT: Proper profile was started/stopped (check via --profile ProfileName on cli)
5. ASSERT: Check that OS 3 connection was created (SSL Cert. was accepted), Docker connection was created, SA state is started (stopped)

Use case 3: CDK 3.2+ Server adapter can operate two profile simultaneously
1. EXEC: There is no old CDK configuration, have CDK with profiles feature downloaded, 'setup-cdk' called - happens out of IDE
2. EXEC: Create New CDK 3.2+ server with default values (profile = minishift)
3. EXEC: Create New CDK 3.2+ server with profile set to value different than "minishift"
4. EXEC: Start default server adapter with default profile
5. ASSERT: Proper profile was started/stopped (check via --profile ProfileName on cli)
6. ASSERT: Check that OS 3 connection was created (SSL Cert. was accepted), Docker connection was created, SA state is started (stopped)
7. EXEC: Start server adapter with named profile set
8. ASSERT: Proper profile was started/stopped (check via --profile ProfileName on cli)
9. ASSERT: Check that OS 3 connection was created (SSL Cert. was accepted), Docker connection was created, SA state is started (stopped)
10. EXEC: Stop named profile
11. ASSERT: Proper profile was started/stopped (check via --profile ProfileName on cli), SA state is stopped
12. EXEC: Stop default profile
13. ASSERT: Proper profile was started/stopped (check via --profile ProfileName on cli), SA state is stopped


> Support the profile feature in CDK server adapter
> -------------------------------------------------
>
>                 Key: JBIDE-25055
>                 URL: https://issues.jboss.org/browse/JBIDE-25055
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: cdk
>    Affects Versions: 4.5.0.Final
>            Reporter: Jeff MAURY
>            Assignee: Rob Stryker
>              Labels: cdk, cdk_server_adapter_, server_adapter
>             Fix For: 4.5.1.AM3
>
>
> Minishift 1.6 brought the notion of profile for running several instances of clusters. According to [~lalatendum] this will land in CDK 3.2 / Freesia
> So we may extend the CDK server adapter to support that feature.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)