We don't have a generate.sh in either apis/apigateway/v1alpha1 or in apis/apigateway/v1beta1. There should be one in both, so that we can generate the types (and mappers) for these resources.
Please read apis/bigtable/v1alpha1/generate.sh for a good example to follow. Pass --multiversion to the generate-mapper command if we are using multiple api versions. Pass --include-skipped-output to generate-types and generate-mapper so that when we skip generating a function, we still render it so that we have something to copy from.
When we then run the generate.sh script(s), it should generate some files and some CRDs; we should then be able to run dev/tasks/diff-crds and ideally we would see no changes to the CRDs.
If there are changes to the CRDs, we will need to probably override the fields in the types so that the generates CRDs are identical (as determined by dev/tasks/diff-crds). It's OK for field descriptions to change, it's not OK for there to be any schema changes.
We don't have a generate.sh in either apis/apigateway/v1alpha1 or in apis/apigateway/v1beta1. There should be one in both, so that we can generate the types (and mappers) for these resources.
Please read
apis/bigtable/v1alpha1/generate.shfor a good example to follow. Pass--multiversionto the generate-mapper command if we are using multiple api versions. Pass--include-skipped-outputto generate-types and generate-mapper so that when we skip generating a function, we still render it so that we have something to copy from.When we then run the
generate.shscript(s), it should generate some files and some CRDs; we should then be able to rundev/tasks/diff-crdsand ideally we would see no changes to the CRDs.If there are changes to the CRDs, we will need to probably override the fields in the types so that the generates CRDs are identical (as determined by
dev/tasks/diff-crds). It's OK for field descriptions to change, it's not OK for there to be any schema changes.