[DSD-9211] mosipdev to mosipqa

[SwapnilWorks-Devops]

Summary by CodeRabbit

• Chores
  • Updated application image reference to a newer version (1.7.x). This ensures the system uses the latest compatible image variant with improvements and updates.

[coderabbitai]

Walkthrough

A single image reference is updated in the release configuration file. The mosipdev/inji-certify-with-plugins:release-0.13.x image is replaced with mosipdev/esignet-with-plugins:release-1.7.x, updating both the image name and version tag.

Changes

Cohort / File(s)	Summary
Image Reference Update release/vidivi/images.txt	Replaces inji-certify-with-plugins image with esignet-with-plugins; updates image repository name and version tag from release-0.13.x to release-1.7.x

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• Straightforward single-line configuration update with no logic changes or structural impact

Possibly related PRs

• [DSD-9180] image moved from dev2 to qa #1349: Updates image references in the same configuration file
• [DSD-9180] image moved from dev2 to qa #1355: Modifies the same file and references the esignet-with-plugins image being introduced
• [DSD-9190] mosipdev to mosipqa #1356: Updates image repository and tagging formats in the same deployment configuration

Suggested reviewers

• ckm007

Poem

🐰 A carrot-eared scribe hops with glee,
Swapping old images for the spree,
From certify-old to esignet-new,
Release 1.7 comes into view! ✨
Deployment configs, fresh as can be! 🚀

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The PR title refers to changing 'mosipdev to mosipqa', but the actual change replaces 'mosipdev/inji-certify-with-plugins' with 'mosipdev/esignet-with-plugins' — the repository/image names change, not the registry prefix conversion claimed in the title.	Update the title to accurately reflect the main change: something like 'DSD-9211 Replace inji-certify image with esignet image' or 'DSD-9211 Update image reference in release/vidivi/images.txt'

✅ 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 e45c3d3 and 95b11dc.

📒 Files selected for processing (1)

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

🔇 Additional comments (1)

release/vidivi/images.txt (1)

1-1: ⚠️ PR title-to-implementation mismatch — registry not updated as stated.

The PR title "DSD-9211 mosipdev to mosipqa" indicates the registry should change from mosipdev to mosipqa. However, the actual change in release/vidivi/images.txt still references mosipdev:

-mosipdev/inji-certify-with-plugins:release-0.13.x release-0.13.x
+mosipdev/esignet-with-plugins:release-1.7.x 1.7.x

Only the image name and version were updated; the registry organization remains mosipdev instead of being changed to mosipqa. This appears incomplete relative to the PR objective. Per the documented image lifecycle, the expected progression is: mosipdev → mosipdev2 → mosipqa → mosipid.

Verify:

1. Whether the registry should be mosipqa/esignet-with-plugins:release-1.7.x per the PR title
2. Whether the image name and version changes (inji-certify → esignet, 0.13.x → 1.7.x) are intentional or if additional scope was inadvertently included

---

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