Skip to content
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] Regenerate for 1.30, fix patches #3680

Open
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

brendandburns
Copy link
Contributor

@brendandburns brendandburns commented Sep 9, 2024

@yue9944882 I regenerated for 1.30 including the fixes for nullable arrays, also fixed up the patches so they applied cleanly.

Ref #3076

Please take a look.

Tests are failing b/c the YAML is being generated with empty lists intead of nulls, I'm not sure this is easily fixable but will investigate.

YAML is fixed, but one JSON test is failing and needs a fix.

Copy link

linux-foundation-easycla bot commented Sep 9, 2024

CLA Not Signed

@k8s-ci-robot k8s-ci-robot added the cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. label Sep 9, 2024
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: brendandburns

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added approved Indicates a PR has been approved by an approver from all required OWNERS files. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Sep 9, 2024
@brendandburns brendandburns changed the title Regenerate for 1.30, fix patches [WIP] Regenerate for 1.30, fix patches Sep 9, 2024
@k8s-ci-robot k8s-ci-robot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Sep 9, 2024
@brendandburns
Copy link
Contributor Author

Ok, I updated this so that empty lists are omitted from YAML dumping and I think that should be ok.

@yue9944882
Copy link
Member

Error:    KubectlDeleteTest.kubectlDelete:216 No requests exactly matched. Most similar request was:  expected:<
DELETE
/apis/batch%2Fv1/batch%2Fv1/namespaces/foo/jobs/bar

[equalToJson]
{
  "propagationPolicy" : "Foreground"
}> but was:<
DELETE
/apis/batch%2Fv1/batch%2Fv1/namespaces/foo/jobs/bar


{
  "dryRun" : [ ],
  "propagationPolicy" : "Foreground"
}>

it looks like k/k api added a new dry-run option for delete API, so we need to align with that. i will append another commit to fix it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants