Closed dionysius closed 1 year ago
Sorry for the long response time. I agree that we can change the logging level in the test.sh
script. However, I'm not sure about the issue you encountered. Testing the generation with the 2 fields that use external types seems correct to me:
| *`quantity`* __Quantity__ | Test for the Quantity type
| *`serviceport`* __link:https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.22/#serviceport-v1-core[$$ServicePort$$]__ | Test for the IntOrString type, although it is the field TargetPort inside of ServicePort
The warn message is not very specfic and a bit confusing: Failed to find type
. It doesn't say that we are only looking for types in the packages of the current project. Maybe Found external type
would be better?
The logging level is maybe better seen as suggestion, change at your will. Looking at my post my k8s references were still at 1.17. Might be possible that an update fixed it.
What I remember was that it took a while to figure out what was causing it. I had to remove properties one by one until the culprit was found. If you could include the type name causing the issue in the error output at least this would be quicker to debug.
Closing due to old k8s api, reopen if issue persist with recent version.
Patch to represent the issue and directly have a testcase
Missing in the patch:
Current test output with the above patch: