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

Deploy Docker Image wizard: password/token for registry is not prefilled even after choosing a connection

    XMLWordPrintable

Details

    • devex #117 July 2016
    • 10
    • Hide
      1. ASSERT: DONT have anything selected in OpenShift explorer
      2. EXEC: in docker explorer: pick "Deploy to OpenShift" in context menu of your image
      3. ASSERT: connection page shows up
      4. EXEC: pick the connection that you unfolded

      Result:
      Connection wizard page shows up. But even after picking and authenticating, password/token is not prefilled in "Deploy an Image" page

      Expected result:
      I should always be able to select my OpenShift connection, I should always have the connection page presented. Ideally either the selected connection in explorer or the most recently used connection should be preselected.
      The password/token should always be prefilled accordingly.

      Show
      ASSERT: DONT have anything selected in OpenShift explorer EXEC: in docker explorer: pick "Deploy to OpenShift" in context menu of your image ASSERT: connection page shows up EXEC: pick the connection that you unfolded Result: Connection wizard page shows up. But even after picking and authenticating, password/token is not prefilled in "Deploy an Image" page Expected result: I should always be able to select my OpenShift connection, I should always have the connection page presented. Ideally either the selected connection in explorer or the most recently used connection should be preselected. The password/token should always be prefilled accordingly.

    Attachments

      Issue Links

        is related to

        Bug - A problem that impairs or prevents the functions of the product. JBIDE-22738 Deploy docker wizard: Image registry URL becomes null when going between Connection and Deploy pages

        • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
        • Closed

        Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBIDE-22593 New application wizard: preselect v3 connection that I most recently used

        • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
        • Closed
        relates to

        Bug - A problem that impairs or prevents the functions of the product. JBIDE-22595 Deploy Docker image wizard: One gets 2 authentication dialogs if you're using a non-conected connection without store pw

        • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
        • Closed

        Task - Represents a small unit of work that is not end-user facing. JBIDE-22756 Connection: various weirdness in token/password implementations

        • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
        • Open

        Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBIDE-22668 Deploy Docker Image wizard: should always present the connection page initially (like all other wizards)

        • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
        • Open

        Activity

          People

            dbocharo@redhat.com Dmitrii Bocharov (Inactive)
            adietish@redhat.com André Dietisheim
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: