Skip to content

release: Plane-EE v3.1.0 - #276

Merged
sriramveeraghanta merged 21 commits into
masterfrom
feat/combined-enterprise-envs
Aug 12, 2026
Merged

release: Plane-EE v3.1.0#276
sriramveeraghanta merged 21 commits into
masterfrom
feat/combined-enterprise-envs

Conversation

@akshat5302

@akshat5302 akshat5302 commented Aug 3, 2026

Copy link
Copy Markdown
Member

What

Combines #271 and #272 into a single PR. Adds 7 new env vars to the plane-enterprise chart across two ConfigMaps, plus documents them in values.yaml, questions.yml, and README.md.

app-vars ConfigMap (templates/config-secrets/app-env.yaml):

GUNICORN_MAX_REQUESTS: "1000"         # env.gunicorn_max_requests
GUNICORN_MAX_REQUESTS_JITTER: "150"   # env.gunicorn_max_requests_jitter
CELERY_TASK_PUBLISH_RETRY: "True"     # env.celery_task_publish_retry
CELERY_BROKER_POOL_LIMIT: "10"        # env.celery_broker_pool_limit
AI_USAGE_AGENT_MAX_TOKENS_BUDGET: ""  # env.pi_envs.ai_usage_agent_max_tokens_budget

pi-api-vars ConfigMap (templates/config-secrets/pi-api-env.yaml):

PLANE_INTERNAL_API_HOST: "http://<release>-api.<ns>.svc.cluster.local:8000"  # hardcoded, not configurable
AI_USAGE_AGENT_MAX_TOKENS_BUDGET: ""  # env.pi_envs.ai_usage_agent_max_tokens_budget
AI_USAGE_ENFORCEMENT_ENABLED: "1"     # env.pi_envs.ai_usage_enforcement_enabled (default: true)

Chart version bumped 3.0.0 → 3.0.1.

Why

Gunicorn / Celery (from INFRA-456, originally #271): A 50% silent CSV export failure rate was traced to Gunicorn worker rotation (--max-requests in the image entrypoint). Each rotation causes a ~10–30 s AMQP reconnect window; without CELERY_TASK_PUBLISH_RETRY, failed publishes are silently dropped, leaving export records stuck in queued. Without a pool limit, stale connections accumulate. These vars expose the tuning knobs needed to fix it.

AI usage envs (from INFRA-465, originally #272): AI_USAGE_AGENT_MAX_TOKENS_BUDGET and AI_USAGE_ENFORCEMENT_ENABLED align the chart with commercial deployment configs for AI token budget enforcement.

PLANE_INTERNAL_API_HOST: Allows pi-api to reach the backend directly over the cluster network instead of going through the ingress.

Scope / behavior

Var ConfigMap(s) Default Changes default behavior?
GUNICORN_MAX_REQUESTS app-vars 1000 Yes — sets rotation limit; image previously hardcoded 1200. Set to 0 to disable.
GUNICORN_MAX_REQUESTS_JITTER app-vars 150 Yes — staggers worker restarts. Set to 0 when rotation is disabled.
CELERY_TASK_PUBLISH_RETRY app-vars True Yes — enables publish retry on all deployments.
CELERY_BROKER_POOL_LIMIT app-vars 10 Yes — bounds the previously unlimited pool. Set to 0 to disable.
AI_USAGE_AGENT_MAX_TOKENS_BUDGET app-vars, pi-api-vars "" No — empty by default, no-op until set.
AI_USAGE_ENFORCEMENT_ENABLED pi-api-vars "1" Yes — enabled by default; set env.pi_envs.ai_usage_enforcement_enabled: false to render "0".
PLANE_INTERNAL_API_HOST pi-api-vars in-cluster URL Only rendered when services.pi.enabled=true (template already gated).

Note on 0 overrides: GUNICORN_MAX_REQUESTS, GUNICORN_MAX_REQUESTS_JITTER, and CELERY_BROKER_POOL_LIMIT support 0 as a meaningful value. Templates intentionally omit | default N to avoid Helm treating 0 as falsy and silently overriding an explicit --set … =0.

Testing

helm lint — clean, 0 failures.

helm template with defaults:

GUNICORN_MAX_REQUESTS: "1000"
GUNICORN_MAX_REQUESTS_JITTER: "150"
CELERY_TASK_PUBLISH_RETRY: "True"
CELERY_BROKER_POOL_LIMIT: "10"
AI_USAGE_AGENT_MAX_TOKENS_BUDGET: ""
PLANE_INTERNAL_API_HOST: "http://test-api.default.svc.cluster.local:8000"
AI_USAGE_ENFORCEMENT_ENABLED: "1"

helm template with --set env.gunicorn_max_requests=0 --set env.gunicorn_max_requests_jitter=0 --set env.celery_task_publish_retry=false --set env.celery_broker_pool_limit=0:

GUNICORN_MAX_REQUESTS: "0"
GUNICORN_MAX_REQUESTS_JITTER: "0"
CELERY_TASK_PUBLISH_RETRY: "False"
CELERY_BROKER_POOL_LIMIT: "0"

Related

🤖 Generated with Claude Code

Summary by CodeRabbit

  • New Features

    • Added configurable live exporter deployment for PDF and DOCX exports.
    • Added export queue and download URL settings.
    • Added API worker rotation, request jitter, task-publish retries, and broker pool controls.
    • Added AI token budgets and usage enforcement settings.
    • Added Slack, GitHub, Bitbucket, and HubSpot connector configuration.
    • Added internal API connectivity settings.
  • Documentation

    • Documented the new deployment, integration, export, and AI settings.
  • Chores

    • Updated the enterprise Helm chart to 3.2.0 and the application to 3.1.0.

akshat5302 and others added 10 commits July 23, 2026 15:47
…v vars

Add GUNICORN_MAX_REQUESTS, GUNICORN_MAX_REQUESTS_JITTER,
CELERY_TASK_PUBLISH_RETRY, and CELERY_BROKER_POOL_LIMIT to the
app-vars ConfigMap so operators can tune worker rotation and broker
pool behaviour without rebuilding the image.

Defaults set to Kubernetes-friendly values (rotation disabled,
publish retry enabled, pool bounded to 10) to eliminate the
silent task-dispatch failures reported in issue #261.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…ERNAL_API_HOST to pi-api

Add to app-vars ConfigMap (configurable via values.yaml):
- GUNICORN_MAX_REQUESTS (default 0 — rotation disabled, recommended for K8s)
- GUNICORN_MAX_REQUESTS_JITTER (default 0)
- CELERY_TASK_PUBLISH_RETRY (default True — prevent silent task drops on AMQP reconnect)
- CELERY_BROKER_POOL_LIMIT (default 10 — bound connection pool to avoid stale accumulation)

Add to pi-api-vars ConfigMap (hardcoded internal cluster URL):
- PLANE_INTERNAL_API_HOST — points directly to the in-cluster API service

Fixes the silent CSV export failures reported in issue #261 where
gunicorn worker rotation caused stale AMQP connections to silently
discard published tasks.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…ETRY

Align with existing boolean pattern (ternary without default) so that
setting celery_task_publish_retry: false in values.yaml is respected.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- IS_SELF_MANAGED hardcoded to "0" in app-vars and pi-api-vars ConfigMaps
- AI_USAGE_AGENT_MAX_TOKENS_BUDGET added to api and pi containers (default: empty)
- AI_USAGE_ENFORCEMENT_ENABLED added to pi containers only (default: 1)
- Bump chart version 3.0.0 → 3.0.1

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@makeplane

makeplane Bot commented Aug 3, 2026

Copy link
Copy Markdown

@coderabbitai

coderabbitai Bot commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

Walkthrough

The Plane Enterprise Helm chart adds a Live exporter Deployment, export queue settings, API runtime controls, connector credentials, and AI usage settings. It updates Plane version references and increments the chart version to 3.2.0.

Changes

Enterprise chart configuration

Layer / File(s) Summary
Live exporter deployment and export settings
charts/plane-enterprise/questions.yml, charts/plane-enterprise/values.yaml, charts/plane-enterprise/templates/workloads/live-exporter.deployment.yaml, charts/plane-enterprise/templates/config-secrets/live-env.yaml, charts/plane-enterprise/README.md
Adds the Live exporter Deployment, RabbitMQ settings, export queue configuration, download URL, resources, and documentation.
API runtime and AI settings
charts/plane-enterprise/questions.yml, charts/plane-enterprise/values.yaml, charts/plane-enterprise/templates/config-secrets/app-env.yaml, charts/plane-enterprise/templates/config-secrets/pi-api-env.yaml, charts/plane-enterprise/README.md
Adds Gunicorn rotation, Celery retry and broker pool settings, the internal API host, and AI usage configuration.
Silo connector configuration
charts/plane-enterprise/questions.yml, charts/plane-enterprise/values.yaml, charts/plane-enterprise/templates/config-secrets/silo.yaml, charts/plane-enterprise/README.md
Adds Slack, GitHub, Bitbucket, and HubSpot connector settings and conditionally rendered credentials.
Release metadata and version documentation
charts/plane-enterprise/Chart.yaml, charts/plane-enterprise/values.yaml, charts/plane-enterprise/questions.yml, charts/plane-enterprise/README.md
Updates the chart version to 3.2.0 and the application version references to 3.1.0.

Estimated code review effort: 3 (Moderate) | ~25 minutes

Sequence Diagram(s)

sequenceDiagram
  participant HelmRelease
  participant LiveExporter
  participant ConfigMapsSecrets
  participant RabbitMQ
  HelmRelease->>LiveExporter: Render enabled Deployment
  HelmRelease->>ConfigMapsSecrets: Render export and broker settings
  ConfigMapsSecrets->>LiveExporter: Inject environment configuration
  LiveExporter->>RabbitMQ: Process export queue jobs
Loading

Possibly related PRs

Suggested reviewers: sriramveeraghanta, mguptahub

Poem

A rabbit charts the export flow,
RabbitMQ helps the jobs to go.
Secrets guide each connector’s call,
AI limits stand for all.
The version hops to three-point-two.

🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (2 warnings)

Check name Status Explanation Resolution
Linked Issues check ⚠️ Warning The PR implements the #271 settings and #272 AI variables, but it omits the required IS_SELF_MANAGED="0" entries. Add IS_SELF_MANAGED="0" to both app-env.yaml and pi-api-env.yaml, then verify the rendered environments.
Out of Scope Changes check ⚠️ Warning The PR adds live-exporter deployment, export queue settings, and Silo connector configuration not required by issues #271 or #272. Move the exporter and connector changes to separate PRs, or update the linked issues to include those requirements.
✅ Passed checks (3 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly identifies the Plane Enterprise v3.1.0 release, which matches the version updates in the changeset.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat/combined-enterprise-envs

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

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@charts/plane-enterprise/README.md`:
- Around line 501-504: Update the API deployment environment-variable table in
README.md to add rows for env.pi_envs.ai_usage_agent_max_tokens_budget,
env.pi_envs.ai_usage_enforcement_enabled, and env.pi_envs.plane_api_host,
matching their defaults and descriptions from questions.yml.

In `@charts/plane-enterprise/templates/config-secrets/app-env.yaml`:
- Line 118: Preserve an explicitly configured zero for
AI_USAGE_AGENT_MAX_TOKENS_BUDGET by replacing the falsy-value defaulting in both
occurrences: charts/plane-enterprise/templates/config-secrets/app-env.yaml:118
and charts/plane-enterprise/templates/config-secrets/pi-api-env.yaml:161. Keep
present values unchanged, or enforce that the input is provided as a string.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 9ae0547b-2283-4a9e-b9a3-46527b3ec35c

📥 Commits

Reviewing files that changed from the base of the PR and between 3c578a2 and 7685fbc.

📒 Files selected for processing (6)
  • charts/plane-enterprise/Chart.yaml
  • charts/plane-enterprise/README.md
  • charts/plane-enterprise/questions.yml
  • charts/plane-enterprise/templates/config-secrets/app-env.yaml
  • charts/plane-enterprise/templates/config-secrets/pi-api-env.yaml
  • charts/plane-enterprise/values.yaml

Comment thread charts/plane-enterprise/README.md
Comment thread charts/plane-enterprise/templates/config-secrets/app-env.yaml
akshat5302 and others added 6 commits August 3, 2026 13:58
Wires env vars defined in silo's env.ts schema that were absent from
the plane-enterprise Helm chart:

**Secrets (connector blocks):**
- SLACK_SIGNING_SECRET — added to the slack connector conditional block
- GITHUB_WEBHOOK_SECRET — added to the github connector conditional block
- Bitbucket connector block (BITBUCKET_CLIENT_ID/SECRET/WEBHOOK_SECRET)
- Flatfile connector block (FLATFILE_API_KEY)
- HubSpot connector block (HUBSPOT_CLIENT_ID/SECRET)

**ConfigMap:**
- API_INTERNAL_BASE_URL — defaults to the same in-cluster API service
  DNS as API_BASE_URL; overridable via env.silo_envs.api_internal_base_url
- IS_SELF_MANAGED — hardcoded "1" (EE deployments are always self-managed)

values.yaml, questions.yml, and README.md updated accordingly.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…ORT_QUEUE_NAME env

- Add live-exporter Deployment (same image as live, LIVE_MODE=exporter, no HTTP port)
- Add AMQP_URL to live-secrets (Secret) for live and live-exporter
- Add EXPORT_QUEUE_NAME to live-vars ConfigMap (default: plane-exports)
- Declare services.live_exporter and env.export_queue_name in values.yaml
- Add Rancher form entries in questions.yml
- Document in README under Live Exporter and live_env_existingSecret sections
- Bump chart version 3.0.0 → 3.1.0

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…ployment

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Defaults to licenseDomain with protocol inferred from SSL settings.
Configurable via env.export_download_base_url.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 2

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
charts/plane-enterprise/README.md (1)

550-574: 🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win

Document connector variables for external Silo Secrets.

When external_secrets.silo_env_existingSecret is set, the chart does not generate the Silo Secret. The External Secrets Config table omits SLACK_SIGNING_SECRET, GITHUB_WEBHOOK_SECRET, BITBUCKET_CLIENT_ID, BITBUCKET_CLIENT_SECRET, BITBUCKET_WEBHOOK_SECRET, FLATFILE_API_KEY, HUBSPOT_CLIENT_ID, and HUBSPOT_CLIENT_SECRET. Add these rows so external-secret deployments can configure the connectors.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@charts/plane-enterprise/README.md` around lines 550 - 574, Update the
External Secrets Config table in the README to document rows for
SLACK_SIGNING_SECRET, GITHUB_WEBHOOK_SECRET, BITBUCKET_CLIENT_ID,
BITBUCKET_CLIENT_SECRET, BITBUCKET_WEBHOOK_SECRET, FLATFILE_API_KEY,
HUBSPOT_CLIENT_ID, and HUBSPOT_CLIENT_SECRET. Match the existing connector
variable naming, defaults, conditional requirements, and descriptions used by
the corresponding services.silo.connectors entries.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@charts/plane-enterprise/Chart.yaml`:
- Around line 8-9: Align the Chart.yaml appVersion with the default image tag by
setting appVersion to 3.0.1, while leaving the chart version unchanged.

In `@charts/plane-enterprise/questions.yml`:
- Around line 354-358: Update the Silo Deployment configuration table in
README.md to document env.silo_envs.api_internal_base_url, including that it
overrides the API internal base URL and an empty value uses the in-cluster API
service URL.

---

Outside diff comments:
In `@charts/plane-enterprise/README.md`:
- Around line 550-574: Update the External Secrets Config table in the README to
document rows for SLACK_SIGNING_SECRET, GITHUB_WEBHOOK_SECRET,
BITBUCKET_CLIENT_ID, BITBUCKET_CLIENT_SECRET, BITBUCKET_WEBHOOK_SECRET,
FLATFILE_API_KEY, HUBSPOT_CLIENT_ID, and HUBSPOT_CLIENT_SECRET. Match the
existing connector variable naming, defaults, conditional requirements, and
descriptions used by the corresponding services.silo.connectors entries.
🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: f89361fb-3b22-4248-9937-f3bd1c56db7a

📥 Commits

Reviewing files that changed from the base of the PR and between 7685fbc and cdf1177.

📒 Files selected for processing (6)
  • charts/plane-enterprise/Chart.yaml
  • charts/plane-enterprise/README.md
  • charts/plane-enterprise/questions.yml
  • charts/plane-enterprise/templates/config-secrets/app-env.yaml
  • charts/plane-enterprise/templates/config-secrets/silo.yaml
  • charts/plane-enterprise/values.yaml
🚧 Files skipped from review as they are similar to previous changes (1)
  • charts/plane-enterprise/templates/config-secrets/app-env.yaml

Comment thread charts/plane-enterprise/Chart.yaml Outdated
Comment thread charts/plane-enterprise/questions.yml Outdated
Comment on lines +354 to +358
- variable: env.silo_envs.api_internal_base_url
label: "API Internal Base URL"
description: "Internal cluster URL for the API service. Defaults to the in-cluster service DNS when left empty."
type: string
default: ""

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Document env.silo_envs.api_internal_base_url in charts/plane-enterprise/README.md.

Line 354 adds a supported override. The Silo Deployment table does not document this key. Add a row that states an empty value uses the in-cluster API service URL.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@charts/plane-enterprise/questions.yml` around lines 354 - 358, Update the
Silo Deployment configuration table in README.md to document
env.silo_envs.api_internal_base_url, including that it overrides the API
internal base URL and an empty value uses the in-cluster API service URL.

akshat5302 and others added 3 commits August 12, 2026 16:52
…g config

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
… 3.2.0

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@akshat5302 akshat5302 changed the title [INFRA-472] - feat(plane-enterprise): add gunicorn/celery, AI usage, and pi-api host envs release: Plane-EE v3.1.0 Aug 12, 2026

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 1

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
charts/plane-enterprise/README.md (1)

458-481: 📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Document the remaining Live exporter settings.

Add rows for env.export_download_base_url and services.live_exporter.pullPolicy. The chart exposes both settings, but this table does not document them.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@charts/plane-enterprise/README.md` around lines 458 - 481, Update the README
settings tables to document the exposed env.export_download_base_url and
services.live_exporter.pullPolicy configuration keys, including their current
defaults and concise descriptions consistent with the surrounding entries.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@charts/plane-enterprise/templates/config-secrets/live-env.yaml`:
- Around line 17-23: Update the local RabbitMQ `AMQP_URL` branch in the live-env
template to include `.Values.services.rabbitmq.servicePort` after the service
hostname, while preserving the existing external URL and empty fallback
branches.

---

Outside diff comments:
In `@charts/plane-enterprise/README.md`:
- Around line 458-481: Update the README settings tables to document the exposed
env.export_download_base_url and services.live_exporter.pullPolicy configuration
keys, including their current defaults and concise descriptions consistent with
the surrounding entries.
🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: b25d1a78-79c5-4323-b10d-51e4a71910a5

📥 Commits

Reviewing files that changed from the base of the PR and between 2d2b4a9 and f4f011b.

📒 Files selected for processing (7)
  • charts/plane-enterprise/Chart.yaml
  • charts/plane-enterprise/README.md
  • charts/plane-enterprise/questions.yml
  • charts/plane-enterprise/templates/config-secrets/live-env.yaml
  • charts/plane-enterprise/templates/config-secrets/silo.yaml
  • charts/plane-enterprise/templates/workloads/live-exporter.deployment.yaml
  • charts/plane-enterprise/values.yaml
🚧 Files skipped from review as they are similar to previous changes (1)
  • charts/plane-enterprise/templates/config-secrets/silo.yaml

Comment on lines +17 to +23
{{- if .Values.services.rabbitmq.local_setup }}
AMQP_URL: "amqp://{{ .Values.services.rabbitmq.default_user }}:{{ .Values.services.rabbitmq.default_password }}@{{ .Release.Name }}-rabbitmq.{{ .Release.Namespace }}.svc.{{ .Values.env.default_cluster_domain | default "cluster.local" }}/"
{{- else if .Values.services.rabbitmq.external_rabbitmq_url }}
AMQP_URL: {{ .Values.services.rabbitmq.external_rabbitmq_url | quote }}
{{- else }}
AMQP_URL: ""
{{- end }}

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

🗄️ Data Integrity & Integration | 🟡 Minor | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

# Inspect whether the RabbitMQ Service consumes the public servicePort value.
fd -e yaml -e yml . charts/plane-enterprise/templates |
  xargs rg -n -C 4 'services\.rabbitmq\.servicePort|rabbitmq.*servicePort|port:|targetPort:'

Repository: makeplane/helm-charts

Length of output: 38940


Include services.rabbitmq.servicePort in the local AMQP_URL.

When servicePort differs from 5672, the generated URL targets the wrong RabbitMQ Service port and connections fail.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@charts/plane-enterprise/templates/config-secrets/live-env.yaml` around lines
17 - 23, Update the local RabbitMQ `AMQP_URL` branch in the live-env template to
include `.Values.services.rabbitmq.servicePort` after the service hostname,
while preserving the existing external URL and empty fallback branches.

@sriramveeraghanta
sriramveeraghanta merged commit 1b568bb into master Aug 12, 2026
1 check passed
@sriramveeraghanta
sriramveeraghanta deleted the feat/combined-enterprise-envs branch August 12, 2026 15:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants