[DSD-9474] image transfer from dev to dev2

[Ivanmeneges]

Summary by CodeRabbit

• Chores
  • Updated service image configuration to reference a different version from the development branch.

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

[coderabbitai]

Walkthrough

A single image reference line in the release/vidivi/images.txt configuration file was updated, replacing the postgres-upgrade image with inji-certify-with-plugins. The repository name, image identifier, and version tag were changed accordingly.

Changes

Cohort / File(s)	Summary
Image Reference Update release/vidivi/images.txt	Replaced mosipdev/postgres-upgrade:release-1.3.x with mosipdev/inji-certify-with-plugins:develop

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

This is a minimal, single-line configuration update requiring straightforward verification that the new image reference is correct and intended.

Possibly related PRs

• [MOSIP-44014] Updated images.txt #1472: Modifies the same images.txt entry by replacing mosipdev/postgres-upgrade with a different image reference (mosipdev/activemq-artemis:2.39.0).
• [DSD-9201] mosipdev to mosipqa #1362: Updates release/vidivi/images.txt and touches the inji-certify-with-plugins image entry with repository/tag changes.
• [DSD-9325] image transfer from mosipdev2 to mosipqa #1411: Swaps a single image reference in release/vidivi/images.txt with a different repository/name and tag combination.

Suggested reviewers

• ckm007

Poem

🐰 A docker image did gently shift,
From postgres to certify—a gift,
The develop branch now takes the stage,
Updating vidivi's compose page,
With one small line, the config's bright! ✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The title references an image transfer but does not clearly describe the actual change: swapping a postgres-upgrade image for an inji-certify-with-plugins image.	Use a more descriptive title that specifies the actual image change, such as 'Replace postgres-upgrade image with inji-certify-with-plugins in release configuration' 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 f2b4402 and 13e1482.

📒 Files selected for processing (1)

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

🔇 Additional comments (1)

release/vidivi/images.txt (1)

1-1: Verify the service swap and version tag choice for a release branch.

This change replaces postgres-upgrade (a database utility image) with inji-certify-with-plugins (a different service), and changes the version tag from release-1.3.x (a released version) to develop (a development/unstable branch). For a pull request targeting release-1.2.0.1, using a develop tag is atypical and introduces instability into a release artifact. Additionally, the functional impact of replacing postgres-upgrade needs clarification.

Please confirm:

1. Is this service swap intentional? (postgres-upgrade → inji-certify-with-plugins)
2. Why is a develop tag being deployed to a release branch instead of a pinned release version?
3. Is this the only change in the file, or are there other image definitions that remain?
4. What is the business/technical reason for this change (referenced in PR title "image transfer from dev to dev2")?

---

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