Conversation
* Plane-EE: Add Email Service configuration to Helm chart * Add TLS certificate configuration for email service in Helm chart * Update Plane version to 1.2.3 and change email service image references to use artifacts.plane.so for consistency across configurations. * Refactor email service configuration: remove webhook URL from values and questions, update email secrets to use ConfigMap, and add readiness probe to email deployment. * Disable email service in values.yaml configuration * Update cert-issuers.yaml to conditionally enable SSL issuer based on ingress or email service configuration * Refactor condition for SSL issuer in cert-issuers.yaml to prioritize ingress configuration
…uration in README (#107) * Update Plane version to v1.9.3 and add email service configuration to Helm chart * Update README to clarify SMTP domain usage for email service * Update Plane version to v1.10.0 in Chart.yaml, questions.yml, README.md, and values.yaml
Contributor
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the 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. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed 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)
Other keywords and placeholders
Documentation and Community
|
* Add intake email domain configuration to Helm chart - Added `env.intake_email_domain` variable to `questions.yml` and `values.yaml` with a default value. - Updated `README.md` to include documentation for the new `intake_email_domain` variable. - Modified `app-env.yaml` to include the new environment variable for email intake functionality. * Update default value for intake email domain in app-env.yaml and remove related entry from README - Set default value for `INTAKE_EMAIL_DOMAIN` in `app-env.yaml` to "intake.example.com". - Removed the `env.intake_email_domain` entry from the README documentation as it is now handled in the configuration file. * Remove intake email domain configuration from questions.yml, values.yaml, and README.md. Update app-env.yaml to use SMTP domain for email intake functionality.
mguptahub
approved these changes
May 23, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Type of Change
Screenshots and Media (if applicable)
Test Scenarios
References