Skip to content

Conversation

kvaps
Copy link
Member

@kvaps kvaps commented Jul 31, 2025

Signed-off-by: Andrei Kvapil kvapss@gmail.com

What this PR does

# kubectl get --raw /apis/apps.cozystack.io/v1alpha1/namespaces/tenant-whmcs/vminstances  | jq .

was showing:

{
  "apiVersion": "apps.cozystack.io/v1alpha1",
  "items": [],
  "kind": "BucketList",
  "metadata": {
    "resourceVersion": "123218712"
  }
}

now it shows:

{
  "apiVersion": "apps.cozystack.io/v1alpha1",
  "items": [],
  "kind": "VMInstanceList",
  "metadata": {
    "resourceVersion": "123218712"
  }
}

Release note

[cozystack-api] fix type for ApplicationList

Summary by CodeRabbit

  • Refactor
    • Improved how application lists are constructed and returned, using a more flexible unstructured format for responses.
    • Enhanced data handling to support new list formats for better compatibility.

@kvaps kvaps requested review from lllamnyp and klinch0 as code owners July 31, 2025 15:19
Copy link
Contributor

coderabbitai bot commented Jul 31, 2025

Walkthrough

The List method in the Application REST handler was refactored to return an unstructured map representing a list of Application resources, instead of a typed ApplicationList struct. The internal logic for collecting and filtering items remains the same, but the response format and construction were changed to use an unstructured approach. Additionally, the ConvertToTable method was updated to handle unstructured lists by converting items back to typed Application objects.

Changes

Cohort / File(s) Change Summary
Application REST List and Table Conversion
pkg/registry/apps/application/rest.go
Refactored List method to build and return an unstructured list of Applications instead of a typed ApplicationList; added error handling for conversion; updated ConvertToTable to handle unstructured lists by converting items to typed Applications; minor formatting cleanup.

Sequence Diagram(s)

sequenceDiagram
    participant Client
    participant REST
    participant Storage

    Client->>REST: List()
    REST->>Storage: Query HelmReleases
    Storage-->>REST: Return HelmRelease list
    REST->>REST: Convert HelmReleases to unstructured Applications
    REST->>REST: Build unstructured ApplicationList with metadata
    REST-->>Client: Return unstructured ApplicationList
Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Suggested labels

bug, size:M

Suggested reviewers

  • lllamnyp
  • klinch0

Poem

A rabbit hopped through code so neat,
Refactored lists—no easy feat!
From structs to maps, the change was made,
Unstructured now, but not afraid.
The log still counts, the flow’s the same,
Applications listed, just a new name!
🐇✨

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.


📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 24b5e1e and f057d92.

📒 Files selected for processing (1)
  • pkg/registry/apps/application/rest.go (3 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • pkg/registry/apps/application/rest.go
⏰ 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). (1)
  • GitHub Check: Build
✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch fix-api-list

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 generate unit tests to generate unit tests for 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.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Summary of Changes

Hello @kvaps, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses a type issue in the cozystack-api by modifying the List method for Application resources. The core change involves transitioning the return type from a strongly-typed Go struct to a more flexible unstructured.Unstructured object, which is a standard practice for representing dynamic Kubernetes API resources. This ensures proper serialization and compatibility when serving ApplicationList objects.

Highlights

  • API Response Type Change: The List method within the pkg/registry/apps/application/rest.go file has been updated to return an *unstructured.Unstructured object instead of a specific *appsv1alpha1.ApplicationList Go struct. This change aligns the API's list response with a more generic and flexible Kubernetes object representation.
  • Dynamic List Construction: The ApplicationList is now constructed dynamically as a map[string]interface{}. This map explicitly defines the apiVersion, kind (derived from r.kindName + "List"), metadata (including ResourceVersion), and the items array, before being wrapped into an unstructured.Unstructured object for return.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in issue comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments or fill out our survey to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

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 (1)
pkg/registry/apps/application/rest.go (1)

377-385: Consider using GVK from REST struct for consistency.

The unstructured list construction looks correct, but consider using the REST struct's GVK instead of hardcoding the apiVersion for better maintainability.

 appList := map[string]interface{}{
-	"apiVersion": "apps.cozystack.io/v1alpha1",
+	"apiVersion": r.gvk.GroupVersion().String(),
 	"kind":       r.kindName + "List",
 	"metadata": metav1.ListMeta{
 		ResourceVersion: hrList.GetResourceVersion(),
 	},
 	"items": items,
 }
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 2fa56fc and 24b5e1e.

📒 Files selected for processing (1)
  • pkg/registry/apps/application/rest.go (2 hunks)
🧰 Additional context used
🧠 Learnings (1)
📓 Common learnings
Learnt from: lllamnyp
PR: cozystack/cozystack#1130
File: hack/e2e-apps/kubernetes.bats:101-101
Timestamp: 2025-07-11T06:11:25.438Z
Learning: In cozystack, the plural form for the Kubernetes custom resource is `kuberneteses.apps.cozystack.io`, not `kubernetes.apps.cozystack.io`. This is defined in the API schema even though it's not grammatically perfect.
⏰ 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). (1)
  • GitHub Check: Build
🔇 Additional comments (3)
pkg/registry/apps/application/rest.go (3)

325-326: LGTM: Clean refactor to unstructured list construction.

The change from typed ApplicationList to an unstructured slice approach is well-implemented. The logic for collecting items remains intact.


380-380: Verify kind construction follows Kubernetes conventions.

The r.kindName + "List" construction for the list kind appears correct and follows standard Kubernetes API conventions for list resources.


387-388: LGTM: Consistent logging and return type updates.

The logging update to use len(items) and return type change to unstructured.Unstructured are consistent with the refactored implementation.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request fixes the return type of the List function for Application resources, making it consistent with other REST methods by returning an unstructured.Unstructured object. The review focuses on ensuring the list items are correctly converted to unstructured objects and that the ConvertToTable function is updated to handle unstructured lists, which is necessary for kubectl get to work correctly.

Signed-off-by: Andrei Kvapil <kvapss@gmail.com>
@kvaps kvaps added the backport Should change be backported on previus release label Jul 31, 2025
@kvaps kvaps merged commit 24807cb into main Aug 1, 2025
19 checks passed
@kvaps kvaps deleted the fix-api-list branch August 1, 2025 12:34
Copy link

github-actions bot commented Aug 1, 2025

Successfully created backport PR for release-0.34:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport Should change be backported on previus release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants