-
Notifications
You must be signed in to change notification settings - Fork 110
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
kctrl package release
creates an invalid OpenAPI spec from Helm Chart
#1630
Comments
I am wondering if this is resolved if PackageBuild does not have a |
I'm doing a pre-pass with |
the issue remains if the
|
I've been looking at possible paths ahead. When a field's value is # a field without an explicit type
anything: null then, kapp-controller could export its OpenAPI v3 schema type by
My personal take is that ^ options are ordered worst to best. Will see whether I can draft a PR for the any approach. Furthermore, authors of Helm chart's can include a JSON schema file |
I don’t think “omitting it from the values schema” is a viable option anywhere in the list. Practically, the chart I was working with when I opened this issue had a handful of these kinds of keys and they were the values that most commonly needed to be set by users of the chart. Leaving them out really feels like the wrong option in that case, especially if you start thinking that the schema is used for automated input UI generation or validation. |
fixes carvel-dev#1630 Signed-off-by: Max Brauer <[email protected]>
fixes carvel-dev#1630 Signed-off-by: Max Brauer <[email protected]>
fixes carvel-dev#1630 Signed-off-by: Max Brauer <[email protected]>
fixes carvel-dev#1630 Signed-off-by: Max Brauer <[email protected]>
What steps did you take:
Given the following:
run
kctrl package release
What happened:
The following, invalid OpenAPIV3 was created. Specifically
.spec.valuesSchema.openAPIv3.properties.credentials.properties.[password|username].type="null"
is invalid asnull
is not a valid type by spec.What did you expect:
I'd have expected a valid type to be put into the schema.
Anything else you would like to add:
It appears if the following had been used, the type would have been
string
.Unfortunately after a run through
ytt
, thenull
s are put into place and that behavior is not preserved. I'd be open to this being the behavior in the place ofnull
as well.Environment:
kubectl get deployment -n kapp-controller kapp-controller -o yaml
and the annotation iskbld.k14s.io/images
): N/Akubectl version
): N/AVote on this request
This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.
👍 "I would like to see this addressed as soon as possible"
👎 "There are other more important things to focus on right now"
We are also happy to receive and review Pull Requests if you want to help working on this issue.
The text was updated successfully, but these errors were encountered: