[SILO-1525] feat(kustomize): add integration event stream env vars + integration-event-consumer component

[Saurabhkmr98]

What

Adds the integration-event-stream feature's env vars to the shared kustomize base ConfigMaps, and a new integration-event-consumer component.

• kustomize/base/configs/app-configmap.yaml: adds INTEGRATION_EVENT_STREAM_EXCHANGE_NAME, INTEGRATION_EVENT_CONSUMER_QUEUE_NAME, INTEGRATION_EVENT_CONSUMER_PREFETCH, INTEGRATION_EVENT_MAX_RAW_BYTES, INTEGRATION_EVENT_PUBLISH_TIMEOUT, INTEGRATION_EVENT_PUBLISH_MAX_RETRIES, INTEGRATION_EVENT_PUBLISH_RETRY_DELAY, INTEGRATION_EVENT_REPUBLISH_BATCH_SIZE, INTEGRATION_EVENT_REPUBLISH_MAX_ATTEMPTS, INTEGRATION_EVENT_REPUBLISH_GRACE_SECONDS, INTEGRATION_EVENT_CLEANER_BATCH_SIZE, INTEGRATION_EVENT_CLEANER_CUTOFF_DAYS, INTEGRATION_EVENT_COLLECTION_NAME to plane-app-vars (picked up by api/worker/beat-worker via their existing envFrom).
• kustomize/base/configs/silo-configmap.yaml: adds INTEGRATION_EVENT_INGEST_ENABLED, INTEGRATION_EVENT_PROVIDERS, INTEGRATION_EVENT_INGEST_TIMEOUT_MS.
• New kustomize/components/integration-event-consumer/ (deployment.yaml + HPA, configmap.yaml, kustomization.yaml) — reuses the backend image, runs ./bin/docker-entrypoint-integration-event-consumer.sh, mirroring the existing agent-consumer component exactly.
• Wires ../../components/integration-event-consumer into overlays/default, overlays/managed, and overlays/phoenix, right next to the existing webhook-consumer/agent-consumer component entries (all three already ship those consumers active, so this one is added active too, not commented-out/optional).

Why

plane-ee's new Integration Event Stream feature (normalized provider-webhook events on a durable RabbitMQ exchange) ships with its own env vars and a reference consumer container (run_integration_event_consumer) that these manifests didn't yet expose.

Scope / behavior

• The shared INTEGRATION_EVENT_* vars land on plane-app-vars/plane-silo-vars unconditionally, but the app code already defaults to the same values when unset, so api/worker/beat-worker/silo behavior doesn't change beyond gaining these keys.
• INTEGRATION_EVENT_INGEST_ENABLED defaults to "0" — Silo ingest stays off until explicitly enabled.
• The new consumer component does deploy by default in default/managed/phoenix (consistent with how webhook-consumer/agent-consumer are already always-on in those overlays), running one replica that just idles on an empty queue until the exchange has traffic.
• No terraform changes — the RabbitMQ broker/exchange is shared infrastructure already provisioned.

Testing

• kubectl kustomize overlays/{default,managed,phoenix} — all three build successfully with the new component included (materialized each overlay's vars.yaml/secrets-vars.yaml from their .example files locally for the test; phoenix additionally needed a placeholder custom-ca/customCA.crt, both pre-existing local-only requirements unrelated to this change).
• Confirmed the new plane-integration-event-consumer-wl/-hpa/-vars resources and all INTEGRATION_EVENT_* keys render correctly in each overlay's output.

🤖 Generated with Claude Code

[makeplane]

Linked to Plane Work Item(s)

• (SILO-1525) Add integration publisher envs in kustomize deployments

This comment was auto-generated by Plane