fix(helm): align Novu services Redis DB index to 2

[dittops]

Summary

• Fixed in-app notifications not being delivered to budadmin frontend
• All Novu services (API, Worker, WS, Embed) were using inconsistent Redis DB index values
• The Worker was publishing notifications to Redis DB index 2, but WS service was listening on DB index 1
• This prevented real-time notification delivery via WebSocket

Changes

• infra/helm/bud/charts/novu/templates/api/deployment.yaml - configurable REDIS_DB_INDEX with default "2"
• infra/helm/bud/charts/novu/templates/worker/deployment.yaml - configurable REDIS_DB_INDEX with default "2"
• infra/helm/bud/charts/novu/templates/ws/deployment.yaml - configurable REDIS_DB_INDEX with default "2"
• infra/helm/bud/templates/extra/novu.yaml - embed service REDIS_DB_INDEX set to "2"

Test plan

• Deploy Helm chart to bud-dev namespace
• Verify all Novu pods restart with REDIS_DB_INDEX=2
• Trigger a notification from budnotify
• Verify in-app notification appears in budadmin dashboard

🤖 Generated with Claude Code

[gemini-code-assist]

Summary of Changes

Hello @dittops, I'm Gemini Code Assist¹! 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 critical bug where in-app notifications were not being delivered due to inconsistent Redis database index configurations across Novu services. By aligning the REDIS_DB_INDEX to '2' for the API, Worker, WebSocket, and Embed services, it ensures that all components communicate using the same Redis instance, thereby restoring real-time notification functionality and improving system reliability.

Highlights

• Notification Delivery Fix: Resolved an issue preventing in-app notifications from being delivered to the budadmin frontend.
• Redis DB Index Alignment: Standardized the Redis DB index across all Novu services (API, Worker, WS, Embed) to '2'.
• Mismatched Redis Configuration: Corrected a critical mismatch where the Worker service published notifications to Redis DB index '2' while the WebSocket service was configured to listen on DB index '1', which was preventing real-time notification delivery.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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 by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

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 pull request 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. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

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. ↩

[gemini-code-assist]

Code Review

This pull request correctly identifies and fixes a critical bug where Novu services were using inconsistent Redis DB indexes, preventing real-time notifications. The changes align the services to use DB index 2.

My review focuses on improving the maintainability and robustness of this fix. I've suggested centralizing the REDIS_DB_INDEX configuration to prevent similar inconsistencies in the future. Specifically:

• For the worker and ws services, I recommend using the same configuration value from api.env since they already share other environment variables from there.
• For the embed service, I suggest parameterizing the hardcoded value to also use this centralized configuration.

These changes will create a single source of truth for the Redis DB index across all Novu services, making the system easier to manage and less prone to configuration errors.

[gemini-code-assist]

To ensure all services consistently use the same Redis DB index and to prevent future misconfigurations, it's best to use a single source of truth. Since this service already uses environment variables from api.env (like NODE_ENV), I recommend using .Values.api.env.REDIS_DB_INDEX here as well. This avoids introducing a new, separate configuration path (.Values.worker.env) that could diverge.

              value : {{ .Values.api.env.REDIS_DB_INDEX | default "2" | quote }}

[gemini-code-assist]

To ensure all services consistently use the same Redis DB index and to prevent future misconfigurations, it's best to use a single source of truth. Since this service already uses environment variables from api.env (like NODE_ENV), I recommend using .Values.api.env.REDIS_DB_INDEX here as well. This avoids introducing a new, separate configuration path (.Values.ws.env) that could diverge.

              value : {{ .Values.api.env.REDIS_DB_INDEX | default "2" | quote }}

[gemini-code-assist]

While changing the value to 2 fixes the immediate issue, hardcoding it makes future maintenance difficult. To ensure this embed service stays aligned with the other Novu services, I recommend parameterizing this value to use the same configuration source. This creates a single point of change for the Redis DB index.

Assuming the novu subchart is referenced with the name novu, you can use its value like this:

            value : {{ .Values.novu.api.env.REDIS_DB_INDEX | default "2" | quote }}