Uploaded image for project: 'Insights Experiences'
  1. Insights Experiences
  2. HMS-6871

Supported and required customizations for image types

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • Image Builder
    • None
    • Supported and required customizations for image types
    • Done
    • image-builder-2
    • 13
    • 0% To Do, 33% In Progress, 67% Done

      The current state of customization and option handling is very hard to follow, error prone, and has many gaps. The logic for all image types for a given distro is contained in a single function checkOptions(). Supported customizations are checked in a series of conditions that are hard to trace. More importantly, when new options are added, there is no requirement to check for the presence or absence of the option for a given image type, which often leads to cases where an option that shouldn't be supported by an image type is instead silently ignored.

      We need a systematic way of enabling options and customizations on each image type explicitly. The same or similar mechanism should be used for the (relatively rare) required customizations.

      Any Blueprint customization or option that is added to should be explicitly listed on all image types that should support it, otherwise it should default to unsupported.

              akoutsou@redhat.com Achilleas Koutsou
              akoutsou@redhat.com Achilleas Koutsou
              None
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: