Open theunrepentantgeek opened 2 years ago
@matthchr can I take it and do it? should I know something more about these fields?
You're welcome to take this issue and do it.
We already handle a bunch of formats - typically, a format gets translated into an underlying type (e.g. IntType
) and some validation rules. For example, byte probably becomes IntType
+ Min: 0 + Max: 255
@theunrepentantgeek can you help me and tell me where or how I can generate a config file for the code generator? or can you attach some an example?
Apologies @PawelHaracz, somehow I missed your message. 😢
If you're still interested (no problem if you're not), I'd suggest reusing the existing configuration file for the generator - v2/azure-arm.yaml
. The commandline to run the generator would look like this:
$ generator gen-types azure-arm.yaml
When the data format is handled, you should see a few small changes in the generated code under v2/api
.
Thank you for your respons. Of course, I want to still try to help you. I gonna try to use this clip and resolve the issue 😃
We're still interested in doing this, although to date we haven't seen many issues with lack of this support.
No change from above.
We still want this. The code has moved to line 270.
Describe the current behavior
During run of the code generator, we get warnings about unsupported property formats:
Describe the improvement
We should add proper support for these formats so that our CRDs properly validate up front.
Additional context
This may technically be a breaking change, as we'll be rejecting values previously accepted - but given they would then be rejected by ARM, I don't think this will negatively impact any current users.