chore: serve files endpoints from API pod

[davidwallacejackson]

Summary by CodeRabbit

• New Features
  • Added a new /files path to the ingress configuration, allowing users to access file-related endpoints when the global API is enabled.
• Chores
  • Updated the application chart version to 0.29.1.

[coderabbitai]

Walkthrough

A new ingress path configuration was introduced in the Helm template for the operator-wandb chart. This addition conditionally creates a /files path in the ingress resource when the global API is enabled. The new path uses a prefix match and routes requests to the same backend service and port as the existing /api and /graphql paths. No other files or control flow mechanisms were modified.

Changes

File(s)	Change Summary
charts/operator-wandb/templates/_ingress.tpl	Added a conditional ingress path block for /files routed to the backend API service on port 8081
charts/operator-wandb/Chart.yaml	Incremented Helm chart version from 0.29.0 to 0.29.1

Sequence Diagram(s)

sequenceDiagram
    participant Client
    participant Ingress
    participant API_Service

    Client->>Ingress: Request to /files/*
    Ingress->>API_Service: Forward to <release-name>-api:8081
    API_Service-->>Ingress: Response
    Ingress-->>Client: Response

Loading

Suggested reviewers

• zacharyblasczyk
• jsbroks
• vanpelt

Poem

In the meadow of code where ingress grows,
A new path for files now gracefully flows.
Through /files it hops, with prefix in tow,
To the backend it scurries, quick as a doe.
The chart is now richer, the routes multiply,
As rabbits and packets together hop by! 🐇

---

📜 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 f514691 and b4f5046.

📒 Files selected for processing (1)

• charts/operator-wandb/Chart.yaml (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• charts/operator-wandb/Chart.yaml

⏰ Context from checks skipped due to timeout of 90000ms (16)

• GitHub Check: Test Chart (v1.29.14, separate-pods)
• GitHub Check: Test Chart (v1.29.14, user-defined-secrets)
• GitHub Check: Test Chart (v1.29.14, executor-enabled)
• GitHub Check: Test Chart (v1.29.14, default)
• GitHub Check: Test Chart (v1.30.10, separate-pods)
• GitHub Check: Test Chart (v1.30.10, user-defined-secrets)
• GitHub Check: Test Chart (v1.30.10, executor-enabled)
• GitHub Check: Test Chart (v1.30.10, default)
• GitHub Check: Test Chart (v1.31.6, separate-pods)
• GitHub Check: Test Chart (v1.31.6, user-defined-secrets)
• GitHub Check: Test Chart (v1.31.6, executor-enabled)
• GitHub Check: Test Chart (v1.31.6, default)
• GitHub Check: Test Chart (v1.32.2, separate-pods)
• GitHub Check: Test Chart (v1.32.2, user-defined-secrets)
• GitHub Check: Test Chart (v1.32.2, executor-enabled)
• GitHub Check: Test Chart (v1.32.2, default)

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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]

Actionable comments posted: 0

🧹 Nitpick comments (1)

charts/operator-wandb/templates/_ingress.tpl (1)

76-82: Consider adding a comment explaining the purpose of the /files endpoint.

While the implementation is correct, adding a brief comment about what types of files are served by this endpoint would improve maintainability and help future developers understand the intent.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 0cf0457 and f514691.

📒 Files selected for processing (1)

• charts/operator-wandb/templates/_ingress.tpl (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (16)

• GitHub Check: Test Chart (v1.29.14, separate-pods)
• GitHub Check: Test Chart (v1.29.14, user-defined-secrets)
• GitHub Check: Test Chart (v1.29.14, executor-enabled)
• GitHub Check: Test Chart (v1.29.14, default)
• GitHub Check: Test Chart (v1.30.10, separate-pods)
• GitHub Check: Test Chart (v1.30.10, user-defined-secrets)
• GitHub Check: Test Chart (v1.30.10, executor-enabled)
• GitHub Check: Test Chart (v1.30.10, default)
• GitHub Check: Test Chart (v1.31.6, separate-pods)
• GitHub Check: Test Chart (v1.31.6, user-defined-secrets)
• GitHub Check: Test Chart (v1.31.6, executor-enabled)
• GitHub Check: Test Chart (v1.31.6, default)
• GitHub Check: Test Chart (v1.32.2, separate-pods)
• GitHub Check: Test Chart (v1.32.2, user-defined-secrets)
• GitHub Check: Test Chart (v1.32.2, executor-enabled)
• GitHub Check: Test Chart (v1.32.2, default)

🔇 Additional comments (1)

charts/operator-wandb/templates/_ingress.tpl (1)

76-82: LGTM - New ingress path configuration for /files looks good.

The addition of this new path with pathType: Prefix correctly routes /files traffic to the API pod, consistent with the existing /api and /graphql paths configuration.

[dacbd]

closing as discussed