Comment 5 for bug 1739646

mnaser: I'm OK with doing the backward compatible thing by default too.

We'd remove the option if/when we have a replacement, which is maybe something that could come out of that spec.

Otherwise we could probably add a microversion in Rocky to indicate if a flavor with disk=0 enforces boot from volume? Just an idea. That gets a bit weird though because the value exposed out of the API wouldn't be part of the flavor resource, it would be from the config in the API at that point in time, because the config could change after the flavor was created. Would definitely require some thought on that.