-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
🐛 ClusterClass: drop support for nullable #5780
🐛 ClusterClass: drop support for nullable #5780
Conversation
@@ -83,9 +83,6 @@ func defaultClusterVariable(clusterVariable *clusterv1.ClusterVariable, clusterC | |||
|
|||
var value interface{} | |||
// If the schema has a default value, default it. | |||
// NOTE: This is essentially the same which the structural schema defaulting | |||
// lib would do, except that it wouldn't default nullable values. | |||
// As we want to also default nullable variables we have to do it ourselves. | |||
if apiExtensionsSchema.Default != nil { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's keep the simple defaulting for this PR. The new full implementation is part of: #5779 (including object/array support)
@@ -132,8 +132,6 @@ func validateSchema(schema *clusterv1.JSONSchemaProps, variableName string, fldP | |||
switch { | |||
case len(apiExtensionsSchema.Type) == 0: | |||
return field.ErrorList{field.Required(fldPath.Child("type"), "openAPIV3Schema.type cannot be empty")} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As we don't want to point to nullable anymore, it's good enough if type == "null"
is handled by the next case.
Diff is fine, |
887670a
to
fdd36ec
Compare
Signed-off-by: Stefan Büringer buringerst@vmware.com
fdd36ec
to
a84739a
Compare
/retest flaky unrelated test |
@sbueringer: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: vincepri The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Signed-off-by: Stefan Büringer buringerst@vmware.com
What this PR does / why we need it:
More context on the issue.
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #5776