[crd-generator] Generated CRD YAML is not always the same when using @PrinterColumn

[clement-buchart]

Hello,

I've been migrating some internal operator from the go-based CRD generation to the Java based one. Thanks for this lib.

A minor inconvenience I noticed is that, when using additional printer column via the @PrinterColumn annotation, the generated YAML may change at each build because the order of the additionalPrinterColumns in the YAML is not consistent.

This cause the digest of the docker image to change each build, which cause our CD to deploy the operator.

My current workaround is something like

yq -j e customresources.yml | jq '.spec.versions[].additionalPrinterColumns|=sort_by(.name)' | yq -P e -

to make the order predictable.

Cheers

[clement-buchart]

Great, thank you very much 👍🏻