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

Fix diff logic for CRD kinds with the same name as a built-in #1779

Merged
merged 2 commits into from
Oct 29, 2021

Conversation

lblackstone
Copy link
Member

Proposed changes

The diff logic was incorrectly treating CRD kinds with a name
matching a built-in kind as known (e.g., Service). In these cases,
the patch behavior was erroneously set to strategic merge rather
than JSON merge.

Related issues (optional)

Fix #1774

The diff logic was incorrectly treating CRD kinds with a name
matching a built-in kind as known (e.g., Service). In these cases,
the patch behavior was erroneously set to strategic merge rather
than JSON merge.
@viveklak
Copy link
Contributor

@lblackstone thanks for the quick fix!

@github-actions
Copy link

Does the PR have any schema changes?

Looking good! No breaking changes found.
No new resources/functions.

2 similar comments
@github-actions
Copy link

Does the PR have any schema changes?

Looking good! No breaking changes found.
No new resources/functions.

@github-actions
Copy link

Does the PR have any schema changes?

Looking good! No breaking changes found.
No new resources/functions.

@github-actions
Copy link

Does the PR have any schema changes?

Looking good! No breaking changes found.
No new resources/functions.

"storage.k8s.io/v1",
"storage.k8s.io/v1alpha1",
"storage.k8s.io/v1beta1",
"v1", // alias for "core/v1"
Copy link
Contributor

Choose a reason for hiding this comment

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

Is there a way to know that we are not missing any other aliases?

Copy link
Member Author

Choose a reason for hiding this comment

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

"core/v1" is the only special case I'm aware of, and is a relic from early versions of k8s. Anything else should include a group and a version.

@lblackstone lblackstone merged commit 0ccfbaa into master Oct 29, 2021
@pulumi-bot pulumi-bot deleted the lblackstone/crd-patch branch October 29, 2021 18:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

CustomResource update fails with "the body of the request was in an unknown format" error
2 participants