Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-19654

Application wizard: Opening the wizard on an account without SSH key opens broken wizard

XMLWordPrintable

    • Hide

      EXEC: Create a new OpenShift v2 connection.
      EXEC: Create (or ensure that there is) a domain under the conection.
      EXEC: Select domain.
      ASSERT: make sure that there is no ssh key present in the connection
      EXEC: Open context menu of a domain and select New - Application...

      RESULT: Broken New application wizard is opened.
      EXPECTED RESULT: SSH Key wizard/dialog is opened and then it proceed to New application wizard.

      Show
      EXEC: Create a new OpenShift v2 connection. EXEC: Create (or ensure that there is) a domain under the conection. EXEC: Select domain. ASSERT: make sure that there is no ssh key present in the connection EXEC: Open context menu of a domain and select New - Application... RESULT: Broken New application wizard is opened. EXPECTED RESULT: SSH Key wizard/dialog is opened and then it proceed to New application wizard.

      If user is opening a New application wizard from domain (context menu on domain item in OpenShift explorer) or shell menu (File - New - OpenShift Application) and there is no SSH key related to v2 account, the wizard is opened directly and cartridge/quickstart selection is empty

      There should be at first opened SSH Key wizard/dialog to let the user add a SSH key to the account and then it should proceed to New application wizard (this is how it worked. Currently it's working like this only on New application wizard opened via context menu of a connection).

        1. prompt-to-upload-keys.png
          prompt-to-upload-keys.png
          36 kB
        2. new_app_wizard.png
          new_app_wizard.png
          47 kB

            adietish@redhat.com André Dietisheim
            mlabuda_jira Marián Labuda (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: