Skip to content

[cozystack-api] Disable startegic-json-patch support - #1179

Merged
Andrei Kvapil (kvaps) merged 1 commit into
mainfrom
disable-smp
Jul 9, 2025
Merged

Andrei Kvapil (kvaps) merged 1 commit into
mainfrom
disable-smp

Conversation

@kvaps

@kvaps Andrei Kvapil (kvaps) commented Jul 9, 2025 •

Copy link
Copy Markdown
Member

Signed-off-by: Andrei Kvapil [email protected]

What this PR does

This PR adds a post-processing hook that removes application/strategic-merge-patch+json from every PATCH operation in the generated OpenAPI v2/v3 specs.

Strategic-merge-patch (SMP) is never supported for CRDs, and our aggregated API implementation can’t handle it either. When the spec advertises SMP, kubectl picks that media-type by default and sends an SMP body, which the apiserver then rejects with
unable to find api field in struct JSON for the json field ….

By dropping SMP from consumes / content:

  • kubectl apply|patch … transparently falls back to
    application/merge-patch+json or application/json-patch+json.
  • Server-side-apply (kubectl apply --server-side …) keeps working via application/apply-patch+yaml.

No changes are required on the handler side—only the advertised media-types are updated.

Release note

[cozystack-api] Disable startegic-json-patch support

@coderabbitai

coderabbitai Bot commented Jul 9, 2025 •

Copy link
Copy Markdown
Contributor

Walkthrough

A new constant for the MIME type "application/strategic-merge-patch+json" was introduced. The OpenAPI v2 and v3 post-processing functions were updated to remove this MIME type from all PATCH operations in the generated OpenAPI documents, ensuring it is no longer advertised as supported.

Changes

File(s) Change Summary
pkg/cmd/server/openapi.go Added smp constant; updated OpenAPI v2 and v3 post-processors to remove smp from PATCH requests

Suggested reviewers

  • lllamnyp
  • klinch0

Poem

A patchy MIME once hopped along,
But now it’s gone, no longer strong.
In OpenAPI’s gentle breeze,
Only the right types, if you please!
The rabbit snips, the docs are neat,
Strategic merge takes a back seat. 🐇✨

✨ Finishing Touches
  • 📝 Generate Docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (2)
pkg/cmd/server/openapi.go (2)

19-19: Consider using a more descriptive constant name.

While smp is concise, a more descriptive name like strategicMergePatchContentType would improve code readability and maintainability.

-	smp         = "application/strategic-merge-patch+json"
+	strategicMergePatchContentType = "application/strategic-merge-patch+json"

205-218: Consider using slices.DeleteFunc for more idiomatic filtering.

The current filtering logic is correct but could be more concise using Go's built-in slice utilities.

-		if op.Patch != nil && len(op.Patch.Consumes) > 0 {
-			var out []string
-			for _, c := range op.Patch.Consumes {
-				if c != smp {
-					out = append(out, c)
-				}
-			}
-			op.Patch.Consumes = out
-			sw.Paths.Paths[p] = op
-		}
+		if op.Patch != nil && len(op.Patch.Consumes) > 0 {
+			op.Patch.Consumes = slices.DeleteFunc(op.Patch.Consumes, func(c string) bool {
+				return c == smp
+			})
+			sw.Paths.Paths[p] = op
+		}

Note: This would require importing slices package (import "slices").

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f32c642 and 23a7281.

📒 Files selected for processing (1)
  • pkg/cmd/server/openapi.go (5 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
  • GitHub Check: Build
  • GitHub Check: pre-commit
🔇 Additional comments (1)
pkg/cmd/server/openapi.go (1)

142-151: LGTM! Clean implementation for OpenAPI v3.

The logic correctly iterates through all paths and removes the strategic-merge-patch+json MIME type from PATCH operations. The null checks are appropriate and the implementation follows the existing code patterns.

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.

1 participant