Skip to content

Conversation

Dav-14
Copy link
Contributor

@Dav-14 Dav-14 commented Apr 17, 2025

No description provided.

@Dav-14 Dav-14 requested a review from a team as a code owner April 17, 2025 15:03
Copy link

coderabbitai bot commented Apr 17, 2025

Walkthrough

This change updates the version numbers for multiple Helm charts across their respective README files and introduces or documents a new podAnnotations configuration key for several charts, allowing users to specify pod-level annotations. Additionally, a new Helm template for pod annotations is added to the core chart. The updates are documentation-focused, with the primary functional addition being support and documentation for podAnnotations in various charts.

Changes

Files/Paths Change Summary
README.md Updated Helm chart versions for Agent, Cloudprem, Console, Console-V3, Core, Membership, Portal, Regions, Stargate.
charts/agent/README.md, charts/regions/README.md Updated version badges; added/clarified podAnnotations documentation for agent and regions charts.
charts/cloudprem/README.md Updated version; added podAnnotations key for console, console-v3, membership, portal components.
charts/console/README.md, charts/console-v3/README.md, charts/membership/README.md, charts/portal/README.md Updated version badges; added podAnnotations key documentation.
charts/core/README.md Updated version badge only.
charts/core/templates/_annotations.tpl Added new Helm template for rendering pod annotations in the core chart.
charts/stargate/README.md Updated version badge.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Helm Chart
    participant Kubernetes

    User->>Helm Chart: Set podAnnotations in values.yaml
    Helm Chart->>Kubernetes: Render manifests with podAnnotations
    Kubernetes-->>User: Deploy pods with specified annotations
Loading

Possibly related PRs

  • formancehq/helm#93: Adds annotations keys for rollout in similar charts, thematically related through annotation configuration changes.
  • formancehq/helm#136: Updates Regions chart version badge, related by version bump for the same chart.
  • formancehq/helm#133: Updates Regions chart version and ledger versions, related by version bump and chart updates.

Suggested reviewers

  • flemzord

Poem

A rabbit hopped through YAML fields,
With podAnnotations freshly revealed.
Version numbers grew,
As documentation flew—
Now Helm charts shine, their secrets unsealed!
🐇✨


📜 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 94b4c46 and cb5f127.

📒 Files selected for processing (1)
  • charts/stargate/README.md (1 hunks)
✅ Files skipped from review due to trivial changes (1)
  • charts/stargate/README.md
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Tests

🪧 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 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

@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: 2

🧹 Nitpick comments (5)
charts/core/templates/_annotations.tpl (1)

1-8: Consider indenting toYaml output

The new core.podAnnotations template correctly renders annotations when .Values.podAnnotations is set. To ensure the YAML lines are properly indented in consuming templates, pipe the output through indent. For example:

- {{ toYaml . }}
+ {{ toYaml . | indent 2 }}
charts/cloudprem/README.md (4)

566-566: Enhance documentation with podAnnotations example
You’ve added console.podAnnotations correctly. Consider including a minimal usage snippet (e.g.:

console:
  podAnnotations:
    my-annotation: "true"

) to illustrate how users can apply custom annotations.


621-621: Enhance documentation with podAnnotations example
The new console-v3.podAnnotations entry is well‑introduced. Adding a brief example YAML block will help users understand its purpose and usage.


699-699: Enhance documentation with podAnnotations example
membership.podAnnotations is documented. A small example of setting membership pod annotations would improve clarity (e.g.:

membership:
  podAnnotations:
    monitoring: "enabled"

).


751-751: Enhance documentation with podAnnotations example
You’ve documented portal.podAnnotations. Including an example snippet demonstrating portal pod annotations will guide users in customizing their deployments.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 1a5417c and c9ed021.

⛔ Files ignored due to path filters (37)
  • charts/agent/Chart.lock is excluded by !**/*.lock, !**/*.lock
  • charts/agent/Chart.yaml is excluded by !**/*.yaml
  • charts/agent/templates/deployment.yaml is excluded by !**/*.yaml
  • charts/agent/values.yaml is excluded by !**/*.yaml
  • charts/cloudprem/Chart.lock is excluded by !**/*.lock, !**/*.lock
  • charts/cloudprem/Chart.yaml is excluded by !**/*.yaml
  • charts/console-v3/Chart.lock is excluded by !**/*.lock, !**/*.lock
  • charts/console-v3/Chart.yaml is excluded by !**/*.yaml
  • charts/console-v3/templates/deployment.yaml is excluded by !**/*.yaml
  • charts/console-v3/values.schema.json is excluded by !**/*.json
  • charts/console-v3/values.yaml is excluded by !**/*.yaml
  • charts/console/Chart.lock is excluded by !**/*.lock, !**/*.lock
  • charts/console/Chart.yaml is excluded by !**/*.yaml
  • charts/console/templates/deployment.yaml is excluded by !**/*.yaml
  • charts/console/values.schema.json is excluded by !**/*.json
  • charts/console/values.yaml is excluded by !**/*.yaml
  • charts/core/Chart.yaml is excluded by !**/*.yaml
  • charts/membership/Chart.lock is excluded by !**/*.lock, !**/*.lock
  • charts/membership/Chart.yaml is excluded by !**/*.yaml
  • charts/membership/templates/cronjob-gc-invitation.yaml is excluded by !**/*.yaml
  • charts/membership/templates/cronjob-gc.yaml is excluded by !**/*.yaml
  • charts/membership/templates/cronjob-stack-lifeycle.yaml is excluded by !**/*.yaml
  • charts/membership/templates/deployment.yaml is excluded by !**/*.yaml
  • charts/membership/templates/job.yaml is excluded by !**/*.yaml
  • charts/membership/values.schema.json is excluded by !**/*.json
  • charts/membership/values.yaml is excluded by !**/*.yaml
  • charts/portal/Chart.lock is excluded by !**/*.lock, !**/*.lock
  • charts/portal/Chart.yaml is excluded by !**/*.yaml
  • charts/portal/templates/deployment.yaml is excluded by !**/*.yaml
  • charts/portal/values.schema.json is excluded by !**/*.json
  • charts/portal/values.yaml is excluded by !**/*.yaml
  • charts/regions/Chart.lock is excluded by !**/*.lock, !**/*.lock
  • charts/regions/Chart.yaml is excluded by !**/*.yaml
  • charts/stargate/Chart.lock is excluded by !**/*.lock, !**/*.lock
  • charts/stargate/Chart.yaml is excluded by !**/*.yaml
  • charts/stargate/templates/deployment.yaml is excluded by !**/*.yaml
  • charts/stargate/values.yaml is excluded by !**/*.yaml
📒 Files selected for processing (11)
  • README.md (1 hunks)
  • charts/agent/README.md (2 hunks)
  • charts/cloudprem/README.md (5 hunks)
  • charts/console-v3/README.md (2 hunks)
  • charts/console/README.md (2 hunks)
  • charts/core/README.md (1 hunks)
  • charts/core/templates/_annotations.tpl (1 hunks)
  • charts/membership/README.md (2 hunks)
  • charts/portal/README.md (2 hunks)
  • charts/regions/README.md (2 hunks)
  • charts/stargate/README.md (2 hunks)
🧰 Additional context used
🪛 LanguageTool
README.md

[style] ~13-~13: Using many exclamation marks might seem excessive (in this case: 10 exclamation marks for a text that’s 2958 characters long)
Context: ...tions, users, roles, and permissions. | Artifact HUB | | Portal | 2.2.0 | v1.0.0 | Formance Portal | Artifact HUB | | Regions | 2.17.0 | latest | Formance Private Regions Helm Chart | Artifact HUB | | Stargate | 0.8.0 | latest | Formance EE Stargate gRPC Gateway | [![Artifact HUB](https://img.shields.io/en...

(EN_EXCESSIVE_EXCLAMATION)

⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Tests
🔇 Additional comments (16)
charts/core/README.md (1)

3-3: Update core chart version badge

The version badge was correctly bumped to 1.3.0 to reflect this release.

charts/agent/README.md (2)

3-3: Bump agent chart version to 2.8.0

The version badge update aligns with the coordinated chart version increments.


68-68: Document podAnnotations value

The addition of the podAnnotations key with default {} and description "pod annotations" is correct and consistent with other charts.

charts/regions/README.md (2)

3-3: Bump regions chart version to 2.17.0

The version badge update is correct and follows the release pattern.


176-176: Add agent.podAnnotations documentation

The new agent.podAnnotations entry with default {} and description "pod annotations" correctly documents the feature.

charts/portal/README.md (2)

3-3: Bump portal chart version to 2.2.0

The version badge update reflects the new release version.


108-108: Document podAnnotations value

The addition of the podAnnotations key under values with default {} and description "pod annotations" is consistent with the PR’s scope.

charts/console-v3/README.md (2)

3-3: Verify version bump to 2.2.0
The version badge update to 2.2.0 looks correct and aligns with the coordinated chart version updates.


108-108: Document new podAnnotations key
The podAnnotations configuration key is now documented with type object, default {}, and description "pod annotations". This aligns with other charts—good addition.

README.md (1)

7-11: Top‑level chart version matrix updated
The chart versions in the matrix have been bumped appropriately for Agent (2.8.0), Cloudprem (3.1.0), Console (2.2.0), Console‑V3 (2.2.0), Core (1.3.0), Membership (2.5.0), Portal (2.2.0), Regions (2.17.0), and Stargate (0.8.0).

Please verify that these version updates match the corresponding charts/*/README.md files, and confirm that the podAnnotations key is documented uniformly across all chart READMEs.

Also applies to: 13-16

charts/stargate/README.md (1)

3-3: Verify version bump to 0.8.0
The version badge has been updated from 0.7.3 to 0.8.0, consistent with the release.

charts/membership/README.md (2)

3-3: Verify version bump to 2.5.0
The version badge update to 2.5.0 aligns with the coordinated release.


241-241: Document new podAnnotations key
The podAnnotations key is now added with type object, default {}, and description "pod annotations", matching the update in other charts.

charts/console/README.md (2)

3-3: Verify version bump to 2.2.0
The version badge has been updated correctly from 2.1.5 to 2.2.0.


105-105: Document new podAnnotations key
The podAnnotations configuration key is now documented under "Other Values" with type object, default {}, and description "pod annotations". This adds consistent support for pod‑level annotations.

charts/cloudprem/README.md (1)

4-4: Ensure version consistency in Chart.yaml
The badge now shows Version 3.1.0 and AppVersion v1.1.0; please verify that the Chart.yaml reflects these updates (version: 3.1.0, appVersion: v1.1.0) and update any related index files or pipeline configurations to prevent mismatches.

@Dav-14 Dav-14 marked this pull request as draft June 5, 2025 10:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants