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

Update gnostic library to point to gnostic-models #118384

Merged
merged 3 commits into from
Jun 2, 2023

Conversation

Jefftree
Copy link
Member

@Jefftree Jefftree commented Jun 1, 2023

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

gnostic OpenAPI components were moved to the gnostic-models library. gnostic is pinned on v0.5.7-v3refs because we did not want to capture the additional dependencies introduced with later versions of gnostic. The OpenAPI component has been moved to gnostic-models so update the library path to reflect that.

This PR also bumps kustomize and kube-openapi to the latest version.

It picks up kubernetes/kube-openapi#403 for a thread safe openapi cache.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?

OpenAPI proto deserializations should use gnostic-models instead of the gnostic library

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:


/triage accepted
/assign @apelisse @sttts

@k8s-ci-robot k8s-ci-robot added the release-note Denotes a PR that will be considered when it comes time to generate release notes. label Jun 1, 2023
@k8s-ci-robot k8s-ci-robot added kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. triage/accepted Indicates an issue or PR is ready to be actively worked on. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. area/apiserver area/cloudprovider area/code-generation area/dependency Issues or PRs related to dependency changes area/kubectl area/test sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. sig/architecture Categorizes an issue or PR as relevant to SIG Architecture. sig/auth Categorizes an issue or PR as relevant to SIG Auth. sig/cli Categorizes an issue or PR as relevant to SIG CLI. sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider. sig/instrumentation Categorizes an issue or PR as relevant to SIG Instrumentation. sig/node Categorizes an issue or PR as relevant to SIG Node. sig/storage Categorizes an issue or PR as relevant to SIG Storage. sig/testing Categorizes an issue or PR as relevant to SIG Testing. and removed do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Jun 1, 2023
@Jefftree
Copy link
Member Author

Jefftree commented Jun 1, 2023

/retest

@bart0sh bart0sh added this to Triage in SIG Node PR Triage Jun 2, 2023
skitt added a commit to skitt/kustomize that referenced this pull request Jun 20, 2023
json-patch was bumped to v5 in k/k as a result of
kubernetes/kubernetes#118384; this aligns with
that, but switches to the v5 module, which is documented as
gopkg.in/evanphx/json-patch.v5.

Signed-off-by: Stephen Kitt <[email protected]>
@Jefftree Jefftree deleted the gnostic-models-branch branch July 31, 2023 14:02
skitt added a commit to skitt/kustomize that referenced this pull request Aug 26, 2023
json-patch was bumped to v5 in k/k as a result of
kubernetes/kubernetes#118384; this aligns with
that, but switches to the v5 module, which is documented as
gopkg.in/evanphx/json-patch.v5.

Signed-off-by: Stephen Kitt <[email protected]>
@@ -568,29 +568,6 @@ func (p Patch) replace(doc *container, op Operation) error {
return errors.Wrapf(err, "replace operation failed to decode path")
}

if path == "" {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it looks like this lost this fix: evanphx/json-patch@50fdc0b

@@ -29,7 +29,7 @@ require (
github.com/docker/distribution v2.8.2+incompatible
github.com/docker/go-units v0.5.0
github.com/emicklei/go-restful/v3 v3.9.0
github.com/evanphx/json-patch v4.12.0+incompatible
github.com/evanphx/json-patch v5.6.0+incompatible
Copy link
Member

@liggitt liggitt Aug 31, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

v5.6.0+incompatible is older than v4.12.0+incompatible (both were tagged on master) ... this dropped the following fix:

evanphx/json-patch@v5.6.0...v4.12.0

do we care about this?

chiukapoor added a commit to chiukapoor/rancher that referenced this pull request Jan 29, 2024
chiukapoor added a commit to chiukapoor/rancher that referenced this pull request Jan 29, 2024
chiukapoor added a commit to chiukapoor/rancher that referenced this pull request Jan 29, 2024
chiukapoor added a commit to chiukapoor/rancher that referenced this pull request Jan 29, 2024
chiukapoor added a commit to chiukapoor/rancher that referenced this pull request Feb 13, 2024
chiukapoor added a commit to chiukapoor/rancher that referenced this pull request Feb 13, 2024
chiukapoor added a commit to chiukapoor/rancher that referenced this pull request Feb 13, 2024
krunalhinguu pushed a commit to krunalhinguu/rancher that referenced this pull request Feb 13, 2024
chiukapoor added a commit to chiukapoor/rancher that referenced this pull request Feb 13, 2024
chiukapoor added a commit to chiukapoor/rancher that referenced this pull request Feb 14, 2024
chiukapoor added a commit to chiukapoor/rancher that referenced this pull request Feb 14, 2024
chiukapoor added a commit to chiukapoor/rancher that referenced this pull request Feb 15, 2024
chiukapoor added a commit to chiukapoor/rancher that referenced this pull request Feb 15, 2024
chiukapoor added a commit to chiukapoor/rancher that referenced this pull request Feb 16, 2024
anupama2501 pushed a commit to anupama2501/rancher that referenced this pull request Mar 5, 2024
chiukapoor added a commit to chiukapoor/rancher that referenced this pull request Apr 10, 2024
chiukapoor added a commit to chiukapoor/rancher that referenced this pull request Apr 17, 2024
chiukapoor added a commit to chiukapoor/rancher that referenced this pull request Apr 18, 2024
chiukapoor added a commit to chiukapoor/rancher that referenced this pull request Apr 19, 2024
chiukapoor added a commit to chiukapoor/rancher that referenced this pull request Apr 23, 2024
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. area/apiserver area/cloudprovider area/code-generation area/dependency Issues or PRs related to dependency changes area/kubectl area/test cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lgtm "Looks good to me", indicates that a PR is ready to be merged. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. release-note Denotes a PR that will be considered when it comes time to generate release notes. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. sig/architecture Categorizes an issue or PR as relevant to SIG Architecture. sig/auth Categorizes an issue or PR as relevant to SIG Auth. sig/cli Categorizes an issue or PR as relevant to SIG CLI. sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider. sig/instrumentation Categorizes an issue or PR as relevant to SIG Instrumentation. sig/node Categorizes an issue or PR as relevant to SIG Node. sig/storage Categorizes an issue or PR as relevant to SIG Storage. sig/testing Categorizes an issue or PR as relevant to SIG Testing. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
Archived in project
Archived in project
Development

Successfully merging this pull request may close these issues.

None yet

7 participants