[DSD-9585] mosipdev2 to mosipqa

[gaganamadival]

Summary by CodeRabbit

• Chores
  • Updated container image references and service versions.

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

[coderabbitai]

Walkthrough

The pull request updates image references in the release configuration by removing a single inji-usecase service image and replacing it with two new inji verification service images, migrating from mosipdev to mosipdev2 registry.

Changes

Cohort / File(s)	Summary
Image Registry Update release/vidivi/images.txt	Removed mosipdev/inji-usecase:truckpass entry and added two new mosipdev2 entries: inji-verify-service:develop and inji-verify-ui:develop, updating registry and service references.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• [MOSIP-43450] mosipdev to mosipdev2 #1510: Performs the inverse operation, consolidating the two mosipdev2 inji verification images back into a single mosipdev inji-usecase entry.
• [DSD-9578] Image transfer from dev to dev2 #1509: Adds the same inji-verify-service and inji-verify-ui entries to the images configuration.
• [DSD-9521] mosipdev2 to mosipqa #1491: Updates image registry references from mosipdev to mosipdev2 in the same configuration file.

Suggested reviewers

• Prafulrakhade

Poem

🐰 Two services spring where one did rest,
From mosipdev to mosipdev2's nest,
Verify and serve with colors anew,
The images dance, develop and brew! 🌟

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The title refers to changing 'mosipdev2 to mosipqa', but the actual changeset replaces one image entry with two new entries from mosipdev/mosipdev2 repositories, which doesn't align with the stated objective.	Update the title to accurately reflect the actual changes, such as 'DSD-9585 Update image references to mosipdev2 services' or clarify what the mosipqa change entails.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

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 @release/vidivi/images.txt:
- Around line 1-2: The two image entries in release/vidivi/images.txt
(mosipdev2/inji-verify-service:develop and mosipdev2/inji-verify-ui:develop) use
the mutable develop tag; replace each with an immutable reference (a fixed
semantic version tag or image digest, e.g. mosipdev2/inji-verify-service:v1.2.3
or mosipdev2/inji-verify-service@sha256:<digest>) to ensure deterministic
deployments, or if develop is intentional for a non-prod environment, add a
clear comment in the file noting this is a mutable development tag and not for
production.

📜 Review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 06daefa and 171d34f.

📒 Files selected for processing (1)

• release/vidivi/images.txt

🔇 Additional comments (2)

release/vidivi/images.txt (2)

1-2: No evidence of inji-usecase in the codebase.

A comprehensive search found zero references to inji-usecase anywhere in the repository. The change shown adds inji-verify-service and inji-verify-ui to release/vidivi/images.txt, but there is no existing inji-usecase service being replaced. This is not a breaking change within this codebase, and no downstream impact assessment is needed unless this change affects external systems outside this repository.

Likely an incorrect or invalid review comment.

---

1-2: Clarify PR intent: Registry transfer direction and image tag stability.

The file correctly shows mosipdev2 as the source registry (consistent with transferring FROM mosipdev2 TO mosipqa), but the PR title should explicitly clarify that this is a source image list for the transfer workflow. Additionally, using the develop tag creates non-deterministic deployments; consider pinning to specific release versions if these images should be stable QA candidates.

[coderabbitai]

⚠️ Potential issue | 🟠 Major

Avoid using mutable develop tag for production deployments.

Both images use the develop tag, which is mutable and can change without notice, leading to non-deterministic deployments. For production or stable environments, pin to specific image digests or immutable version tags. If this is intended for a development environment, document this decision clearly.

🤖 Prompt for AI Agents

In @release/vidivi/images.txt around lines 1 - 2, The two image entries in
release/vidivi/images.txt (mosipdev2/inji-verify-service:develop and
mosipdev2/inji-verify-ui:develop) use the mutable develop tag; replace each with
an immutable reference (a fixed semantic version tag or image digest, e.g.
mosipdev2/inji-verify-service:v1.2.3 or
mosipdev2/inji-verify-service@sha256:<digest>) to ensure deterministic
deployments, or if develop is intentional for a non-prod environment, add a
clear comment in the file noting this is a mutable development tag and not for
production.