Uploaded image for project: 'Red Hat Internal Developer Platform'
  1. Red Hat Internal Developer Platform
  2. RHIDP-11057

Automate component upgrades via Pull Request after template version upgrades

XMLWordPrintable

    • [Doc] Automate component upgrades via Pull Request after template version upgrades
    • M
    • False
    • Hide

      None

      Show
      None
    • False
    • RHDHPLAN-479Automate component upgrades via Pull Request after template version upgrades
    • Done
    • RHDHPLAN-479 - Automate component upgrades via Pull Request after template version upgrades
    • QE Needed, Docs Needed, TE Needed, Customer Facing, PX Needed
    • 0% To Do, 0% In Progress, 100% Done
    • Hide
      Automated Software Template lifecycle management::

      With this update, you can automatically synchronize security updates and configuration changes from Software Templates to downstream repositories. As a result, applications remain compliant and consistent with their source templates without the need for manual file comparisons.

      For more information about enabling and configuring this feature, see {streamline-software-development-and-management-in-rhdh-book-link}#automated_software_template_lifecycle_management/index[Automated Software Template lifecycle management].
      Show
      Automated Software Template lifecycle management:: With this update, you can automatically synchronize security updates and configuration changes from Software Templates to downstream repositories. As a result, applications remain compliant and consistent with their source templates without the need for manual file comparisons. For more information about enabling and configuring this feature, see {streamline-software-development-and-management-in-rhdh-book-link}#automated_software_template_lifecycle_management/index[Automated Software Template lifecycle management].
    • Enhancement
    • Done
    • RHDH AI Sprint 3285

      EPIC Goal

      What are we trying to solve here?

      Background/Feature Origin

      Why is this important?

      User Scenarios

      Dependencies (internal and external)

      Acceptance Criteria

      Release Enablement/Demo - Provide necessary release enablement details and documents
      DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
      DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
      DEV - Downstream build attached to advisory: <link to errata>
      QE - Test plans in Playwright: <link or reference to playwright>
      QE - Automated tests merged: <link or reference to automated tests>
      DOC - Downstream documentation merged: <link to meaningful PR>

              rhn-support-pabel Priyanka Kantem
              rhdh-jirabot RHDH Jirabot
              RHDH Documentation
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: