Skip to content

feat(generic-service): add initContainer support to worker deployment#83

Open
Glenn-Ewing wants to merge 1 commit into
mainfrom
chore/worker-init-container-support
Open

feat(generic-service): add initContainer support to worker deployment#83
Glenn-Ewing wants to merge 1 commit into
mainfrom
chore/worker-init-container-support

Conversation

@Glenn-Ewing

Copy link
Copy Markdown

Summary

  • Adds initContainer support to worker-deployment.yaml, matching the identical pattern already in frontend-deployment.yaml
  • Gated by $value.initContainer.enabled == true so it's opt-in and backwards-compatible with all existing worker configs

Why

The communications-service migration guard (showmigrations --check) is being moved from the PHP frontend deployment to the Python worker deployments as PHP is deprecated. This template change is required to support that.

Test plan

  • Verify a worker with initContainer.enabled: true renders the initContainers block in the generated manifest
  • Verify a worker without initContainer set renders cleanly with no initContainers block

Depends on: devops-cicd PR that moves the migration guard from frontend-ou to the four Python workers (giving-worker, messaging-worker, communications-worker, sites-worker) — that PR needs this chart version published before the helmrelease version can be bumped.

🤖 Generated with Claude Code

Mirrors the existing frontend-deployment.yaml pattern so workers can
gate startup on a pre-flight check (e.g. Django showmigrations --check).

Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
@Glenn-Ewing Glenn-Ewing requested a review from a team as a code owner June 16, 2026 15:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant