[DSD-9226] image movement from dev2 to qa

[gaganamadival]

Summary by CodeRabbit

• Chores
  • Updated deployment image configuration to reference new service repositories and development branch versions

[coderabbitai]

Walkthrough

Updated image repository references in the vidivi release configuration from mosipdev to mosipdev2 for inji-verify-service and inji-verify-ui components, switching deployment branches from release-0.x versions to the develop branch.

Changes

Cohort / File(s)	Summary
Vidivi Image Configuration release/vidivi/images.txt	Replaced two legacy image entries (mosipdev/mimoto on release-0.20.x and mosipdev/inji-web on release-0.15.x) with new repository references (mosipdev2/inji-verify-service and mosipdev2/inji-verify-ui), both pinned to develop branches.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• Single file modification with straightforward image repository and branch replacements
• No business logic or functional behavior changes
• Changes are repetitive and easy to verify against expected image naming conventions

Possibly related PRs

• move images from dev2 to qa #1358: Updates same release/vidivi/images.txt file with mosipdev2-related image repository migrations
• [DSD-9189] moved image from dev to dev2 #1352: Modifies identical entries for inji-web and mimoto image references, transitioning between repository versions
• [DSD-9218] Image transfer from dev to dev2. #1366: Adds inji-verify-service and inji-verify-ui image entries to the same configuration file with alternative repository structure

Poem

🐰 From mosipdev's old nest we hop,
To mosipdev2, we'll never stop!
Release branches fade, develop grows bright,
inji-verify services shine in the light! ✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The title references 'dev2 to qa' environment movement, but the changeset actually involves replacing mosipdev/* images with mosipdev2/* images while switching branch strategies (release branches to develop branches).	Revise the title to accurately describe the main change: something like 'Update images from mosipdev to mosipdev2 with develop branch strategy' would better reflect the actual repository and branch updates.

✅ 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.

✨ Finishing touches

🧪 Generate unit tests (beta)

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

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between dbefabb and 43a614e.

📒 Files selected for processing (1)

• release/vidivi/images.txt (1 hunks)

🔇 Additional comments (1)

release/vidivi/images.txt (1)

1-2: Verify PR objectives alignment and file completeness.

The PR title states "image movement from dev2 to qa," but the changes show updates to the mosipdev2 registry. Please clarify:

1. Is the movement direction correctly described in the PR title? (The changes appear to be updating to mosipdev2, not from it.)
2. Is this the complete file, or are there additional removals not shown?
3. Per the AI summary, previous entries referenced mosipdev/mimoto and mosipdev/inji-web — confirm these have been properly replaced/removed.

Both lines follow consistent formatting with matching develop tags on each side, but without visibility into the full change context and the PR's actual deployment intent, I'd recommend confirming the scope.

---

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.}