-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[crd-gen] Possibility to add extra information to fields #3768
Comments
This issue has been automatically marked as stale because it has not had any activity since 90 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions! |
+1 |
Is this still applicable? Is there still interest on this? |
Someone was asking for something similar on SO recently: https://stackoverflow.com/questions/78028591/fabric8-crd-generator-is-it-possible-to-generate-crd-yaml-with-x-kubernetes-va I think it's still compelling, but let see ... |
This issue has been automatically marked as stale because it has not had any activity since 90 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions! |
Is your enhancement related to a problem? Please describe
The most self-explanatory example is the type format hint allowed in the CRD such as:
Currently the generator emits only the
type
information and we don't have, at best of my knowledge, any way to express a specificformat
.I'm opening this ticket more widely in the hope that we can agree on a solution that will cover additional use-cases:
x-kubernetes-list-type
pattern
format
default
nullable
but I'm open to evaluate specific solutions (e.g. one per missing property).
Describe the solution you'd like
A possible solution, again, is a new custom annotation, even if some of those fields might be extracted more automagically by the generator (e.g.
nullable
anddefault
).Describe alternatives you've considered
No response
Additional context
cc. @metacosm
The text was updated successfully, but these errors were encountered: