Update volume names for feature/zappa-migration

[rudransh-shrivastava]

Proposed change

Resolves #3203

Update volume names

Checklist

• Required: I read and followed the contributing guidelines
• Required: I ran make check-test locally and all tests passed
• I used AI for code, documentation, or tests in this PR

[coderabbitai]

Summary by CodeRabbit

• Chores
  • Updated internal container configuration to enhance infrastructure management and consistency across services.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

Walkthrough

The pull request updates volume names in the Docker Compose local configuration file by systematically renaming all volumes with a "-zappa" suffix across multiple services, including both service-level references and top-level volume declarations.

Changes

Cohort / File(s)	Summary
Docker Compose Local Configuration docker-compose/local/compose.yaml	Renamed all volume identifiers to "-zappa" suffix variants (e.g., backend-venv → backend-venv-zappa, cache-data → cache-data-zappa, etc.) across backend, cache, db, docs, frontend, and worker services; updated service-level volume references and top-level volume declarations accordingly.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Possibly related PRs

• Update volume names #3102: Modifies the same docker-compose/local/compose.yaml file with volume renaming to "-e2e" suffixes rather than "-zappa" variants, indicating parallel migration patterns.

Suggested reviewers

• arkid15r
• kasya

Pre-merge checks and finishing touches

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically describes the main change: updating volume names for the zappa migration feature.
Description check	✅ Passed	The description references the linked issue and states the proposed change is to update volume names, which aligns with the changeset modifications.
Linked Issues check	✅ Passed	The code changes update volume names with -zappa suffixes as intended by issue #3203 to support the feature/zappa-migration work.
Out of Scope Changes check	✅ Passed	All changes are scoped to updating volume names in the Docker Compose configuration file for the zappa migration feature, with no unrelated modifications detected.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 930cc03 and 31e6381.

📒 Files selected for processing (1)

• docker-compose/local/compose.yaml

🧰 Additional context used

🧠 Learnings (5)

📓 Common learnings

Learnt from: rudransh-shrivastava
Repo: OWASP/Nest PR: 3205
File: docker-compose/local.yaml:32-32
Timestamp: 2026-01-05T16:20:39.976Z
Learning: In the OWASP/Nest repository, feature branches use unique volume name suffixes in docker-compose files to prevent volume clashes across parallel development efforts. For example, the feature/nest-zappa-migration branch uses `-zappa` suffix for all volume names (backend-venv-zappa, cache-data-zappa, db-data-zappa, etc.) to ensure isolated environments when switching between branches.

📚 Learning: 2026-01-05T16:20:39.976Z

Learnt from: rudransh-shrivastava
Repo: OWASP/Nest PR: 3205
File: docker-compose/local.yaml:32-32
Timestamp: 2026-01-05T16:20:39.976Z
Learning: In the OWASP/Nest repository, feature branches use unique volume name suffixes in docker-compose files to prevent volume clashes across parallel development efforts. For example, the feature/nest-zappa-migration branch uses `-zappa` suffix for all volume names (backend-venv-zappa, cache-data-zappa, db-data-zappa, etc.) to ensure isolated environments when switching between branches.

Applied to files:

• docker-compose/local/compose.yaml

📚 Learning: 2025-12-26T06:08:58.549Z

Learnt from: ahmedxgouda
Repo: OWASP/Nest PR: 3041
File: .github/workflows/run-ci-cd.yaml:233-243
Timestamp: 2025-12-26T06:08:58.549Z
Learning: Ensure Redis image versions stay in sync across all environments by updating every relevant YAML file together (docker-compose files and CI/CD workflow configurations). When upgrading Redis, bump the image version in all docker-compose files and in all CI workflow YAMLs in one coordinated change to maintain parity across production, staging, local, E2E, and CI tests.

Applied to files:

• docker-compose/local/compose.yaml

📚 Learning: 2025-09-21T17:04:48.154Z

Learnt from: rudransh-shrivastava
Repo: OWASP/Nest PR: 2178
File: frontend/src/app/snapshots/[id]/page.tsx:0-0
Timestamp: 2025-09-21T17:04:48.154Z
Learning: User rudransh-shrivastava confirmed that suggested type safety improvements during Apollo Client migration were no longer relevant, reinforcing their preference to keep migration PRs focused on core migration changes rather than additional improvements.

Applied to files:

• docker-compose/local/compose.yaml

📚 Learning: 2025-10-23T19:22:23.811Z

Learnt from: rudransh-shrivastava
Repo: OWASP/Nest PR: 2431
File: infrastructure/main.tf:0-0
Timestamp: 2025-10-23T19:22:23.811Z
Learning: In Zappa-based serverless deployments, Lambda functions and IAM execution roles are managed by Zappa at application deployment time (via `zappa deploy`/`zappa update`), not via Terraform. Terraform provisions the supporting infrastructure (VPC, RDS, S3, security groups, RDS Proxy, Secrets Manager), while Zappa handles the Lambda orchestration layer.

Applied to files:

• docker-compose/local/compose.yaml

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (4)

• GitHub Check: Run backend tests
• GitHub Check: Run frontend e2e tests
• GitHub Check: Run frontend unit tests
• GitHub Check: CodeQL (javascript-typescript)

🔇 Additional comments (1)

docker-compose/local/compose.yaml (1)

33-33: LGTM! Volume naming strategy correctly implements feature branch isolation.

All volume names have been systematically updated with the -zappa suffix across all services (backend, cache, db, docs, frontend, worker) and properly declared at the top level. The implementation is complete and consistent:

• Shared volumes correctly reference the same name (e.g., backend-venv-zappa used by both backend and worker services)
• All service-level volume references match their top-level declarations
• Naming convention aligns with the repository's feature branch isolation strategy

Based on learnings, this approach prevents volume conflicts when developers switch between feature branches, ensuring clean isolated environments for parallel development efforts.

Also applies to: 52-52, 69-69, 86-86, 108-109, 138-138, 144-149

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

Fix all issues with AI Agents 🤖

In @docker-compose/local.yaml:
- Line 32: This change renames Docker volumes (e.g., backend-venv-zappa,
db-data-zappa) which will create new empty volumes and cause data loss for devs;
either revert the volume renames or provide migration steps: add a migration
script that copies data from the old volume names to the new ones (using a short
container-based copy routine), update CONTRIBUTING.md/PR description with
step-by-step migration commands and a clear warning, and add a note to
CHANGELOG/Release notes marking this as a breaking change so developers know to
run the migration before `docker-compose up`.

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1cac680 and 930cc03.

📒 Files selected for processing (1)

• docker-compose/local.yaml

🧰 Additional context used

🧠 Learnings (2)

📚 Learning: 2025-10-23T19:22:23.811Z

Learnt from: rudransh-shrivastava
Repo: OWASP/Nest PR: 2431
File: infrastructure/main.tf:0-0
Timestamp: 2025-10-23T19:22:23.811Z
Learning: In Zappa-based serverless deployments, Lambda functions and IAM execution roles are managed by Zappa at application deployment time (via `zappa deploy`/`zappa update`), not via Terraform. Terraform provisions the supporting infrastructure (VPC, RDS, S3, security groups, RDS Proxy, Secrets Manager), while Zappa handles the Lambda orchestration layer.

Applied to files:

• docker-compose/local.yaml

📚 Learning: 2025-12-26T06:08:58.549Z

Learnt from: ahmedxgouda
Repo: OWASP/Nest PR: 3041
File: .github/workflows/run-ci-cd.yaml:233-243
Timestamp: 2025-12-26T06:08:58.549Z
Learning: Ensure Redis image versions stay in sync across all environments by updating every relevant YAML file together (docker-compose files and CI/CD workflow configurations). When upgrading Redis, bump the image version in all docker-compose files and in all CI workflow YAMLs in one coordinated change to maintain parity across production, staging, local, E2E, and CI tests.

Applied to files:

• docker-compose/local.yaml

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)

• GitHub Check: Run pre-commit checks
• GitHub Check: CodeQL (javascript-typescript)

🔇 Additional comments (1)

docker-compose/local.yaml (1)

143-148: Volume declarations are consistent with service mounts.

The volume declarations correctly match all the updated volume references in the services above. The syntax is clean and follows Docker Compose best practices.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud