[DSD-9297] move image from dev to dev2

[gaganamadival]

Summary by CodeRabbit

• Chores
  • Updated container image references in development configuration.

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

[coderabbitai]

Walkthrough

The pull request updates a container image reference in the release configuration file. The image source is changed from mosipdev/inji-certify-with-plugins:release-0.13.x to mosipdev/uitest-signup:develop, along with corresponding tag updates.

Changes

Cohort / File(s)	Summary
Image Reference Update release/vidivi/images.txt	Updated container image reference from mosipdev/inji-certify-with-plugins:release-0.13.x release-0.13.x to mosipdev/uitest-signup:develop develop

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• Verify that the new image mosipdev/uitest-signup:develop is the correct replacement and exists in the repository
• Confirm the tag change from release-0.13.x to develop is intentional

Possibly related PRs

• [DSD-9235] IMage transfe from dev to dev2 . #1387: Modifies the same configuration file by replacing image entries with different mosipdev image references.
• [DSD-9189] moved image from dev to dev2 #1352: Updates the same file and directly changes the mosipdev/inji-certify-with-plugins image reference.
• [/DSD-9312] move image from dev to dev2 #1409: Edits the same file and replaces the same mosipdev/inji-certify-with-plugins:release-0.13.x image entry.

Poem

🐰 A hop, skip, and image swap,
From certify to signup we flop,
Develop branch leads the way,
Old tags gone, new ones stay,
Configuration hops along! 📦

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The title mentions moving an image 'from dev to dev2', but the actual change updates the image from mosipdev/inji-certify-with-plugins:release-0.13.x to mosipdev/uitest-signup:develop, which doesn't match the stated source/destination.	Update the title to accurately reflect the actual change, such as 'DSD-9297 Update image reference from inji-certify-with-plugins to uitest-signup' or similar.

✅ 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 840ddcb and 5ee2c8e.

📒 Files selected for processing (1)

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

🔇 Additional comments (1)

release/vidivi/images.txt (1)

1-1: Verify: Using develop tag and test image on release branch.

This change replaces a release-tagged image (inji-certify-with-plugins:release-0.13.x) with a develop-tagged test image (uitest-signup:develop) on the release-1.2.0.1 branch. This is semantically unusual—release branches typically reference stable, release-tagged images rather than development or test images.

Additionally, the PR title mentions "move image from dev to dev2," but the actual change appears to be moving to a different image (uitest-signup) and a develop tag, not a secondary dev environment. Please clarify:

• Is this intentional and part of the release strategy?
• Does this match the intended scope described in the PR title?
• Should the images.txt file on a release branch reference develop tags?

---

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