The case-correcting conversions previously introduced weren't being used for the Status->Spec conversion required by asoctl, resulting in the generated YAML files containing the incorrect values (which is an issue given Kubernetes validation is case-strict, not case-forgiving).
We update the property conversions to handle the new case and regenerate the api files.
What this PR does / why we need it:
The case-correcting conversions previously introduced weren't being used for the Status->Spec conversion required by
asoctl, resulting in the generated YAML files containing the incorrect values (which is an issue given Kubernetes validation is case-strict, not case-forgiving).We update the property conversions to handle the new case and regenerate the api files.
Special notes for your reviewer:
Closes #3805
How does this PR make you feel:
If applicable: