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

Do not allow latest schema version to be impacted by RCs

    • Icon: Task Task
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • None
    • Product / Portfolio Work
    • False
    • Hide

      None

      Show
      None
    • False
    • 0

      When releasing ACS we bump the latest vulnerability schema to the latest release tag. When the release tag is not published, we fallback to RC, which allow the release candidates to pull vulns when performing tests and validations.

      But when doing so we are effectively changing the production bundle to be built on RC-based code.

      Although this is not generally an issue (because bundles are backward compatible), if we submit a change to the release branch that is backward incompatible (by mistake, by lack of knowledge, etc), we can impact production environments.

      The goal of this task is to revisit this decision and try to mitigate this risk.

              jvmartin@redhat.com J. Victor Martins
              jvmartin@redhat.com J. Victor Martins
              ACS Scanner
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: