[jbosstools-issues] [JBoss JIRA] (JBIDE-25170) Using empty profile in CDK 3.2+ server adapter should work with cdk's default profile (minishift)

[Ondrej Dockal (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-25170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ondrej Dockal updated JBIDE-25170:
----------------------------------
    Steps to Reproduce: 
1. EXEC: Have cdk 3.2.x binary downloaded
2. EXEC: Create CDK 3.2+ adapter with no profile set
3. EXEC: Prepare cdk: call setup-cdk on cli
4. ASSERT: calling 'minishift profile list' returns '- minishift Does Not Exist (active)'
5. EXEC: Start CDK 3.2+ server adapter
6. ASSERT: Adapter is started, 'minishift profile list' returns '- minishift Running (active)'
7. EXEC: Add new CDK 3.2+ called test and set profile to ie. 'test'
8. EXEC: call 'minishift setup-cdk --profile test' -> this will set active profile to 'test'
9. ASSERT: 'minishift profile list' returns two profiles where profile 'test' is active
10. EXEC: Start CDK 3.2+ test server adapter
11. ASSERT: CDK 3.2+ test SA is started
12. ASSERT: 'minishift profile list' shows two running profiles and 'test' is active
13. EXEC: Stop CDK 3.2+ default server adapter (the one without profile set)
14. ASSERT: CDK 3.2+ adapter is stopped - FAIL
15. ASSERT: 'minishift profile list' shows that default 'minishift' profile is stopped - FAIL
Instead, active profile 'test' was stopped, because stop operation was not passed with --profile ProfileName flag, which should be in this case 'minishift' to stop proper adapter/profile.

  was:
1. EXEC: Have cdk 3.2.x binary downloaded
2. EXEC: Create CDK 3.2+ adapter with no profile set
3. EXEC: Prepare cdk: call setup-cdk on cli
4. ASSERT: calling 'minishift profile list' returns ''
5. EXEC: Start CDK 3.2+ server adapter
6. ASSERT: Adapter is started, 'minishift profile list' returns '- minishift Running (active)'
7. EXEC: Add new CDK 3.2+ called test and set profile to ie. 'test'
8. EXEC: call 'minishift setup-cdk --profile test' -> this will set active profile to 'test'
9. ASSERT: 'minishift profile list' returns two profiles where profile 'test' is active
10. EXEC: Start CDK 3.2+ test server adapter
11. ASSERT: CDK 3.2+ test SA is started
12. ASSERT: 'minishift profile list' shows two running profiles and 'test' is active
13. EXEC: Stop CDK 3.2+ default server adapter (the one without profile set)
14. ASSERT: CDK 3.2+ adapter is stopped - FAIL
15. ASSERT: 'minishift profile list' shows that default 'minishift' profile is stopped - FAIL
Instead, active profile 'test' was stopped, because stop operation was not passed with --profile ProfileName flag, which should be in this case 'minishift' to stop proper adapter/profile.



> Using empty profile in CDK 3.2+ server adapter should work with cdk's default profile (minishift)
> -------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-25170
>                 URL: https://issues.jboss.org/browse/JBIDE-25170
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: cdk
>    Affects Versions: 4.5.1.AM3
>            Reporter: Ondrej Dockal
>
> I have two running CDK 3.2+ server adapters, and if I operate the one where profile is not defined (I would expect that it is set to default one aka 'minishift') it works with actually active profile. 



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