This APB should consume kubevirt.yaml release about kubevirt-apb HOT 4 CLOSED

Correct me if I'm wrong @karmab, but @karmab used his project https://github.com/karmab/ttapb to generate the playbooks from https://github.com/kubevirt/kubevirt/blob/master/manifests/release/kubevirt.yaml.in. With this tool, we could regenerate the playbooks on a per commit basis to kubevirt.yaml.in.

from kubevirt-apb.

@rthallisey if it is like this, then I don't have problem with it.
And think there should be process to regenerate it on every kubevirt release.

Just note: I think it should be generated from released manifest, no? For example: https://github.com/kubevirt/kubevirt/releases/download/v0.2.0/kubevirt.yaml instead of kubevirt.yaml.in.

from kubevirt-apb.

@lukas-bednar I think that makes sense when we tag a release for the apb so we're right in sync with kubevirt release. But during the development cycle, I think we want to pull from the latest templates so developers will always have the latest bits.

from kubevirt-apb.

indeed the idea is to use the tooling to generate the playbook from the release file ( this is what i did and now i updated the tool to also allow prior rendering of template )
i also believe that at some point, the tool ( which intends to be generic, not kubevirt specific) wont be needed as only the targetted version will change and not the manifests per se

from kubevirt-apb.