[DSD-9652] injistackdev to injistackdev2

[gaganamadival]

Summary by CodeRabbit

• Chores
  • Updated image references in configuration files, transitioning from release branch to development branch versions. Replaced three development image entries with two updated ones to reflect current build requirements.

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

[coderabbitai]

Walkthrough

This PR updates the release/vidivi/images.txt file by removing three image entries referencing mosipdev images at release-1.3.x and adding two new image entries from injistackdev at the develop branch.

Changes

Cohort / File(s)	Change Summary
Image Configuration Update release/vidivi/images.txt	Removed three mosipdev image entries (pmp-ui-v2, partner-management-service, policy-management-service) from release-1.3.x and added two injistackdev image entries (inji-certify-with-plugins, apitest-inji-certify) from develop branch

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• [DSD-9279] move images from dev to dev2 #1398 — Modifies the same file and removes the identical three mosipdev image entries from release-1.3.x
• [DSD-9625] move from mosipdev to mosipdev2 #1519 — Introduces a reference to injistackdev/inji-certify-with-plugins image in the same configuration file
• [DSD-9636] Image transfer from injistackdev to injistackdev2 #1523 — Directly affects the injistackdev/apitest-inji-certify image entry added in this PR

Suggested reviewers

• Prafulrakhade

Poem

🐰 A hop through the images so bright,
Releasing old versions to flight,
Dev branches rise,
New docker supplies,
The vidivi stack shines ever right! ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The PR title references 'injistackdev to injistackdev2', but the actual changes involve replacing mosipdev images with injistackdev images pointing to develop branch, not injistackdev2.	Update the title to accurately reflect the main change, such as 'DSD-9652 Replace release-1.3.x images with develop branch injistackdev images' or 'DSD-9652 Update images to injistackdev develop branch'.

✅ 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: Update the two image references in release/vidivi/images.txt
so they use the renamed registry `injistackdev2` (replace
`injistackdev/inji-certify-with-plugins:develop` and
`injistackdev/apitest-inji-certify:develop` with `injistackdev2/...`), and also
decide whether a `develop` tag is appropriate for this release—if not, change
the tag to the intended release tag (e.g., a version or `latest`) or document
why `develop` should remain; ensure both image strings are updated consistently.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

# First, check if the file exists and examine its content
cat -n release/vidivi/images.txt

Repository: mosip/release-script

Length of output: 182

---

🏁 Script executed:

# Search for references to injistackdev2 in the codebase to verify if it's a valid/existing registry/organization
rg "injistackdev2" --type-list

Repository: mosip/release-script

Length of output: 453

---

🏁 Script executed:

# Search for other references to injistackdev to understand the pattern
rg "injistackdev" -A 2 -B 2 --max-count=20

Repository: mosip/release-script

Length of output: 220

---

🏁 Script executed:

# Check the directory structure around the images.txt file
ls -la release/vidivi/

Repository: mosip/release-script

Length of output: 543

---

🏁 Script executed:

# Check git history for this file to understand the change context
git log --oneline -10 release/vidivi/images.txt

Repository: mosip/release-script

Length of output: 112

---

🏁 Script executed:

# Get more detailed info about recent commits affecting this file
git log -1 --format="%H %ae %ai %s" release/vidivi/images.txt

Repository: mosip/release-script

Length of output: 219

---

🏁 Script executed:

# Search for any references to the issue DSD-9652 or PR title context
rg "DSD-9652|injistackdev2" -i

Repository: mosip/release-script

Length of output: 46

---

🏁 Script executed:

# Check if there's any documentation or comments explaining the change
rg "inji-certify|apitest-inji" -B 3 -A 3

Repository: mosip/release-script

Length of output: 220

---

Images do not match commit intent—replace injistackdev with injistackdev2.

The commit message "[DSD-9652] injistackdev to injistackdev2" indicates a rename to injistackdev2, but the code contains injistackdev on both lines. Update the image registry names to match the stated intent, or clarify why the images were not changed.

Additionally, consider whether using develop branch images in a release context is appropriate; develop branches are typically unstable for production releases.

🤖 Prompt for AI Agents

In `@release/vidivi/images.txt` around lines 1 - 2, Update the two image
references in release/vidivi/images.txt so they use the renamed registry
`injistackdev2` (replace `injistackdev/inji-certify-with-plugins:develop` and
`injistackdev/apitest-inji-certify:develop` with `injistackdev2/...`), and also
decide whether a `develop` tag is appropriate for this release—if not, change
the tag to the intended release tag (e.g., a version or `latest`) or document
why `develop` should remain; ensure both image strings are updated consistently.