Dusty Mabe

hmm. AFAIK there isn't a limit that is being imposed anywhere. Maybe a technical limitation? Either way if you want a custom ISO with some extra bits added on top...

I guess another thing to consider here is how we'd want to represent this in say the `bootc status` output. I think it would be important enough to represent there...

> Wouldn't CoreOS want to support factory resets rerunning Ignition? Then we'd have to special case re-pulling the provisioning image. Indeed. There would be some tradeoff here. > > Is...

Another thing something this could be useful for would be [local layering use cases](https://gitlab.com/fedora/bootc/tracker/-/issues/4) where you don't to upgrade to the thing in the registry unless it's newer than the...

Already had talked to @nikita-dubrovskii on this one so it's scheduled for him for next sprint. It would be good to have more people involved in design and code review,...

May be better to have a separate namespace for staging images. Something like `quay.io/fedora-development`.

Two largish change suggestions: 1. We consider the "platform" here to be `live` and not `live-iso`. This means `platform.live-iso.ipp.yaml -> platform.live.ipp.yaml` and that generates the ISO/PXEkernel/initrd/rootfs. 2. we rename the...

successor in https://github.com/coreos/coreos-assembler/pull/3976

opened as draft to gather feedback on the implementation. still learning rust and not confident in everything I'm doing.

> Ask seems reasonable, though how about we structure it differently so it's instead keyed into the include mechanism, where vars in included manifests could be templated using vars defined...