-
Notifications
You must be signed in to change notification settings - Fork 4
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
[WIP] API-1835: json-patch integration test #49
base: master
Are you sure you want to change the base?
[WIP] API-1835: json-patch integration test #49
Conversation
@p0lyn0mial: This pull request references API-1835 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the epic to target the "4.18.0" version, but no target version was set. In response to this: 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 openshift-eng/jira-lifecycle-plugin repository. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: p0lyn0mial 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 |
@@ -241,7 +241,7 @@ func allPossibleListFileLocations(sourceFS fs.FS, requestInfo *apirequest.Reques | |||
|
|||
namespaces, err := allNamespacesWithData(sourceFS) | |||
if err != nil { | |||
return nil, fmt.Errorf("unable to read namespaces: %w", err) | |||
return allPossibleListFileLocations, fmt.Errorf("unable to read namespaces: %w", err) |
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.
it seems that requiring namespaces
is not necessary when the input contains only cluster-scoped-resources
(my test), wdyt?
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.
@p0lyn0mial: The following tests failed, say
Full PR test history. Your PR dashboard. 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-sigs/prow repository. I understand the commands that are listed here. |
@@ -215,6 +215,9 @@ func (mrt *writeTrackingRoundTripper) roundTrip(req *http.Request) ([]byte, erro | |||
ret.SetNamespace(serializedRequest.ActionMetadata.Namespace) | |||
if actionHasRuntimeObjectBody { // TODO might be able to do something generally based on discovery if absolutely necessary | |||
ret.SetGroupVersionKind(bodyObj.GetObjectKind().GroupVersionKind()) | |||
} else | |||
{ | |||
ret.SetGroupVersionKind(schema.GroupVersionKind{Group: gvr.Group, Version: gvr.Version, Kind: "Authentication"}) |
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.
kube returns the patched/updated object (full obj) in the response, so we need at least an empty GVK. We could use discovery for this, wdyt?
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.
yes, let's get that fixed.
@@ -0,0 +1 @@ | |||
[{"op":"test","path":"/status/conditions/2/type","value":"WebhookAuthenticatorCertApprover_OpenShiftAuthenticatorDegraded"},{"op":"remove","path":"/status/conditions/2"}] |
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.
want to format these in the future, one per line?
No description provided.