[DSD-9190] mosipdev to mosipqa

[SwapnilWorks-Devops]

Summary by CodeRabbit

• Chores
  • Updated container image registry references with namespace qualification for standardized deployment configuration.

[coderabbitai]

Walkthrough

Image references in the configuration file are updated by prefixing them with mosipdev/ to create fully qualified repository paths. All other tag components including version information remain unchanged. Single file modified with homogeneous, repetitive pattern application.

Changes

Cohort / File(s)	Change Summary
Image repository qualification release/vidivi/images.txt	All image references prefixed with mosipdev/ namespace to create fully qualified repository paths (e.g., esignet-with-plugins → mosipdev/esignet-with-plugins); version tags and suffixes preserved

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• Single file with homogeneous, repetitive prefix additions across all entries
• Configuration-only changes with no logic or behavioral modifications
• Straightforward pattern verification needed

Possibly related PRs

• [DSD-9190] mosipdev to mosipqa #1354: Modifies the same image configuration file by replacing mosipdev/ image entries with alternative references
• [DSD-9166] Image transfer from dev to int #1347: Updates release/vidivi/images.txt to add/replace mosipdev/* image line entries
• [DSD-9189] moved image from dev to dev2 #1352: Changes image repository prefixes in the same configuration file across different namespace variations

Suggested reviewers

• ckm007

Poem

🐰 With prefixes bright, the images align,
Each docker path now fully defined,
mosipdev stamps each reference true,
The namespace dance—a clean debut! 📦✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The PR title indicates a change from 'mosipdev' to 'mosipqa', but the raw summary shows changes updating image references to use 'mosipdev/' prefix, which is the opposite direction.	Update the title to accurately reflect the changes: either 'Add mosipdev image registry prefix' or similar, depending on the actual intent of the changeset.

✅ 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 db0f1b3 and 7172b0e.

📒 Files selected for processing (1)

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

🔇 Additional comments (1)

release/vidivi/images.txt (1)

1-7: Verify the registry prefix matches PR intent.

The PR title "DSD-9190 mosipdev to mosipqa" suggests a migration to mosipqa, but all changes add mosipdev/ as the prefix. This discrepancy needs clarification—should these be mosipqa/ instead, or is the PR title referring to a different aspect of the change?

Please confirm:

1. Is mosipdev/ the intended registry prefix, or should it be mosipqa/?
2. Are all 7 image references in this file the only ones that need updating?

---

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