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

Automatic content snapshotting

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • Image Builder
    • None
    • Automatic content snapshotting
    • False

      When user rebuilds a blueprint, the image can be completely different even when blueprint does not change.

      Image builder should automatically store snapshot for RPM repositories (the ID or snapshot name/date), resolved bootc repository commit (sha256) and in the future all content input that can change the result.

      Then when user rebuilds a blueprint that was already built, image builder can check latest snapshot and/or bootc tag and if there is newer content available, user can be asked if they mean to rebuild the original content or rebase to the latest version. If they choose to rebase, a new blueprint version is created with the latest snapshots/commits and image can be built.

      This is currently not possible for 3rd party repositories, user should be warned when 3rd party repos are active.

      This is an idea I wanted to record in Jira, feel free to elaborate or discuss it here.

              Unassigned Unassigned
              rhn-engineering-lzapletal Lukáš Zapletal
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: