walters added a new comment to an issue you are following:
``
Yeah, having to regenerate images just to get a new commit ID is a bit annoying. Down the
line, I think we should go to automatic in place updates. Once we do that across the
board, the cloud images are more of an asynchronous starting point - in other words, we
don't necessarily respin the AMIs/qcow2 etc. for each release.
This becomes more of a polar opposite from the current "image-focused, ostree is a
lookaside" approach. Now, I'm well aware that there is a *large* contingent of
public cloud users who basically just want updated AMIs (and/or respin their own), and
don't care about in place updates (whether ostree or not).
Going down a rabbit hole a bit, one thing we could conceive of is moving away from the
ostree commit history. This would get more natural if we used Docker/OCI for transport.
Really, the only thing causing the commit IDs to differ is the parent history (and
timestamp, but we control that). There'd be a lot of tradeoffs in this...but it's
a conceptual question as to how useful the ostree history really is.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/6545