Uploaded image for project: 'OpenShift Java Client'
  1. OpenShift Java Client
  2. OSJC-135

Find associated resources that caused a resource to be deployed

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Done
    • Major
    • 3.0.0
    • 3.0.0
    • core

    Description

      Add capabilities to be able to trace which resources are associated with a deployed resource. For example, to establish a "pipeline" from a deployed resource (e.g. Pod), OS adds annotations to source the 'deployment', deploymentconfig, and template. This will allow us to present that logical chain to the user.

      Attachments

        Issue Links

          blocks

          Feature Request - Feature requests from customers and/or users JBIDE-19000 As a user I want to browse the resources for my projects

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Feature Request - Feature requests from customers and/or users JBIDE-19178 Explorer, Servers view: Add deployment view to OpenShift v3 explorer

          • 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

          Feature Request - Feature requests from customers and/or users JBIDE-21524 Explorer, Servers view: Add deployment view to OpenShift v3 explorer

          • 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-20972 As a user I want to see relevant but simple info about my OpenShift v3 server adapter in the servers view

          • 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

              jcantril@redhat.com Jeffrey Cantrill
              jcantril@redhat.com Jeffrey Cantrill
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: