Migrate Docker CD production workflow from Azure Container Registry to Docker Hub

[Copilot]

Removes all Azure Container Registry dependencies from the production deployment workflow. The workflow now uses Docker Hub exclusively for all build jobs.

Changes

• build-base job: Replace azure/docker-login@v1 with docker/login-action@v3 using DOCKERHUB_USERNAME and DOCKERHUB_TOKEN secrets
• build-languages job: Replace azure/docker-login@v1 with docker/login-action@v3 using DOCKERHUB_USERNAME and DOCKERHUB_TOKEN secrets
• Deployment summary: Remove undefined registry output reference

All four build jobs now authenticate to Docker Hub consistently. Removed secret dependencies: REGISTRY_URL, ACR_USERNAME, ACR_PASSWORD.

# Before
- name: Log in to Azure Container Registry
  uses: azure/docker-login@v1
  with:
    login-server: ${{ env.REGISTRY_URL }}
    username: ${{ secrets.ACR_USERNAME }}
    password: ${{ secrets.ACR_PASSWORD }}

# After
- name: Login to Docker Hub
  uses: docker/login-action@v3
  with:
    username: ${{ secrets.DOCKERHUB_USERNAME }}
    password: ${{ secrets.DOCKERHUB_TOKEN }}

Original prompt

WE ARE USING DOCKER HUB FOR STORING OF CONTAIENR IN CICD PLEASE UPDATE CICD REMOVE ALL AZURE RELATED STUFF IN THIS FILE

TAKE REFERANCE OTHER CICD ACTION ALL SECREAT ARE ALREADY CONFIGURED IN GITHUB WORKFLOW

PLEASE READ DOCKER FOLDER then figure out it
.github/workflows/docker-cd-production.yml

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

Summary by CodeRabbit

• Chores
  • Updated deployment infrastructure configuration for container image management

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

The pull request replaces Azure Container Registry authentication with Docker Hub authentication in the Docker CI/CD production workflow. Three workflow stages were updated to use Docker Hub credentials and the newer docker/login-action@v3 action. Registry information was removed from deployment summary output.

Changes

Cohort / File(s)	Summary
Docker Hub Authentication Migration \.github/workflows/docker-cd-production\.yml	Replaced Azure Container Registry login steps with Docker Hub login across three workflow stages; swapped docker-login@v1 with docker/login-action@v3; updated credentials from ACR login-server to DOCKERHUB_USERNAME and DOCKERHUB_TOKEN; removed registry echo line from deployment summary output

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Verify Docker Hub credentials environment variables (DOCKERHUB_USERNAME, DOCKERHUB_TOKEN) are properly configured in the repository secrets
• Confirm the updated action version docker/login-action@v3 is appropriate and stable
• Ensure all three workflow stages correctly use the new authentication mechanism

Poem

🐰 From Azure's tower to Docker's hub so bright,
We hop along the workflow, getting auth just right!
Three stages now authenticated with renewed delight,
The registry changed, but our builds run tonight! 🐳

Pre-merge checks and finishing touches

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Description Check	⚠️ Warning	The pull request description provides substantive technical content explaining what was changed and why (migration from ACR to Docker Hub, specific jobs affected, before/after code examples), but it does not follow the required template structure. The description is missing several key template sections including the Type of Change checkboxes, Testing checkboxes, Related Issue link, the code review Checklist, and Environment Tested information. While the core description content is clear and not vague or off-topic, the lack of template compliance and missing critical structural elements means the description does not meet the expected standards for this repository.	Update the pull request description to follow the provided template structure. Add the Type of Change section (mark this as "Code refactoring" or "Infrastructure update"), include the Testing section with appropriate checkboxes marked, optionally fill in the Related Issue if applicable, complete the code review Checklist items, and add Environment Tested and Additional Notes sections where relevant. This will ensure the description meets the repository's standard for pull request documentation.
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The pull request title "Migrate Docker CD production workflow from Azure Container Registry to Docker Hub" is clear, concise, and directly related to the main changeset. It accurately summarizes the primary objective of replacing Azure Container Registry authentication with Docker Hub authentication across the production deployment workflow. A teammate scanning the repository history would immediately understand this is a migration from one container registry service to another, which aligns with the detailed changes documented in the pull request.

---

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

[VAIBHAVSING]

@coderabbitai review

[coderabbitai]

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.