Uploaded image for project: 'Red Hat Advanced Cluster Security'
  1. Red Hat Advanced Cluster Security
  2. ROX-30735

Use RP(A) templating to provide even fewer manual stuff in advisories

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • None

      See: https://konflux.pages.redhat.com/docs/users/releasing/releasing-with-an-advisory.html#releaseplan-collectors-and-templating

      Example in use: https://gitlab.cee.redhat.com/rhtap-release/advisories/-/blob/15dd408a3a29db5c134d97a01ddc269dba02c21b/data/advisories/acm-multicluster-glo-tenant/2025/22572/advisory.yaml#L251

      This time, let's consider templating. There's a separate ROX-31268 for collectors.

      Also: check how we can put floating tags ("4.8", "4.9") in RPAs.

      Update the release document after implementing the changes (and testing on stage release pipelines).

      Addendum 1:
      As part of this process, let's consider not including the highest severity of fixed CVE at the beginning of the synopsis, because the generated advisory already calculates and shows that severity right below the synopsis. (Get agreement from ProdSec before doing this.

      Slack thread (this message and following)

      Example of a typo in a stage release that brought this to light:

        1. Screenshot 2025-12-17 at 7.39.45 AM.png
          Screenshot 2025-12-17 at 7.39.45 AM.png
          162 kB

              Unassigned Unassigned
              msugakov@redhat.com Misha Sugakov
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: