Uploaded image for project: 'WINDUP - Red Hat Application Migration Toolkit'
  1. WINDUP - Red Hat Application Migration Toolkit
  2. WINDUP-3240

Windup Technology Reports - Introduce new tiers in preparation for the new technology tags.

    XMLWordPrintable

Details

    • Task
    • Resolution: Done
    • Major
    • None
    • None
    • MTA CLI
    • None
    • False
    • False
    • Hide
      * *Why we missed the bug?*
       ** Pick to proper answer from drop-down field upper.
       +_Additional comments:_+


       * *What is required:*
       ** Pick to proper answer from drop-down field upper.
       +_Additional comments:_+
      Show
      * *Why we missed the bug?*  ** Pick to proper answer from drop-down field upper.  +_Additional comments:_+  * *What is required:*  ** Pick to proper answer from drop-down field upper.  +_Additional comments:_+
    • ---
    • ---
    • Sprint 212 AMM, Sprint 213 AMM, Sprint 214 AMM

    Description

      We will be introducing a number of new columns the technology Bubblemap report (Googlesheet).

      Connect

      Streaming

      Store

      No SQL Database

      Sustain

      Resource Management

      Configuration Management

      Observability

      Execute

      Utilities

      Serverless / FAAS

      Each new category must be placed in alphabetic order within it's parent category

      If the sub tiers need to be uniquely named, as we already have an Other then the Other under Execute can be called Utilities.

      This Jira must make whatever changes to the Windup core necessary so that when a technology is allocated to a tier and a row (either "Java EE" or "Embedded") via a  name-usage.windup.xml rule it appears in the correct location on the technology grid and bubblemap.

       
      <technology-identified name="kafka-streams">
      <tagname="Connect"/>
      <tagname="Embedded"/>
      <tagname="Streaming"/>
      </technology-identified>
       

       

       

       

       

      Attachments

        1. Observability.png
          Observability.png
          13 kB
        2. temp.zip
          5 kB

        Issue Links

          blocks

          Task - Represents a small unit of work that is not end-user facing. WINDUPRULE-802 Tech Tags - Spring Boot Actuator*

          • 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.
          • Dev Complete

          Task - Represents a small unit of work that is not end-user facing. WINDUPRULE-804 Tech Tags - Spring Cloud Config*

          • 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.
          • Dev Complete

          Task - Represents a small unit of work that is not end-user facing. WINDUPRULE-808 Tech Tags - Spring JMX*

          • 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.
          • Dev Complete

          Task - Represents a small unit of work that is not end-user facing. WINDUPRULE-809 Tech Tags - Spring Properties*

          • 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.
          • Dev Complete

          Task - Represents a small unit of work that is not end-user facing. WINDUPRULE-812 Tech Tags - Spring Shell*

          • 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.
          • Dev Complete

          Activity

            People

              rhn-support-sshveta Shveta Sachdeva
              pcattana Philip Cattanach
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: