[DSD-9652] injistackdev2 to injistackqa - #1527
Conversation
Signed-off-by: gaganamadival <94885434+gaganamadival@users.noreply.github.com>
WalkthroughUpdated the manifest file to replace a single Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (2 passed)
✏️ 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. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In `@release/vidivi/images.txt`:
- Around line 1-2: Update the two image entries using mutable :develop tags and
the old registry: replace injistackdev2/inji-certify-with-plugins:develop and
injistackdev2/apitest-inji-certify:develop with images hosted on injistackqa and
pinned to immutable version tags or digests (e.g.,
injistackqa/inji-certify-with-plugins:<version> or `@sha256`:<digest> and
injistackqa/apitest-inji-certify:<version> or `@sha256`:<digest>) so the release
manifest is reproducible and the registry migration is applied.
| injistackdev2/inji-certify-with-plugins:develop develop | ||
| injistackdev2/apitest-inji-certify:develop develop |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
# First, check if the file exists and read its contents
cat -n release/vidivi/images.txt 2>/dev/null || echo "File not found or inaccessible"Repository: mosip/release-script
Length of output: 184
🏁 Script executed:
# Check for any PR context or related files that might indicate the objective
git log --oneline -20 2>/dev/null | head -20 || echo "Git history not available"Repository: mosip/release-script
Length of output: 111
🏁 Script executed:
# Look for any documentation or comments about the registry change
find . -type f \( -name "*.md" -o -name "*.txt" -o -name "*.yml" -o -name "*.yaml" \) -exec grep -l "injistackqa\|injistackdev2" {} \; 2>/dev/null | head -20Repository: mosip/release-script
Length of output: 91
🏁 Script executed:
# Check for similar image files and understand the format
find release -name "*.txt" -type f | head -10Repository: mosip/release-script
Length of output: 168
🏁 Script executed:
# Look for documentation on how these images.txt files are used
find . -type f \( -name "*.md" -o -name "*.sh" \) -exec grep -l "images.txt" {} \; 2>/dev/null | head -10Repository: mosip/release-script
Length of output: 117
🏁 Script executed:
# Check the structure around this file to understand context
ls -la release/vidivi/ 2>/dev/nullRepository: mosip/release-script
Length of output: 543
🏁 Script executed:
# Check the README files to understand the format and purpose
cat -n release/vidivi/README.md | head -100Repository: mosip/release-script
Length of output: 5153
🏁 Script executed:
# Also check the other images.txt for reference
cat -n release/checks/images.txtRepository: mosip/release-script
Length of output: 3165
🏁 Script executed:
# Check config.yml to understand the context
cat -n release/vidivi/config.ymlRepository: mosip/release-script
Length of output: 445
Update registry and pin immutable tags for reproducible releases.
The file uses mutable :develop tags, which breaks reproducibility in a release manifest. Additionally, the PR objective is to migrate from injistackdev2 to injistackqa, but the registry has not been updated. Replace with immutable tags or digests (following the pattern in release/checks/images.txt, which uses specific version tags like 1.2.0).
Suggested fix pattern
-injistackdev2/inji-certify-with-plugins:develop develop
-injistackdev2/apitest-inji-certify:develop develop
+injistackqa/inji-certify-with-plugins:<immutable-tag-or-digest> <version>
+injistackqa/apitest-inji-certify:<immutable-tag-or-digest> <version>🤖 Prompt for AI Agents
In `@release/vidivi/images.txt` around lines 1 - 2, Update the two image entries
using mutable :develop tags and the old registry: replace
injistackdev2/inji-certify-with-plugins:develop and
injistackdev2/apitest-inji-certify:develop with images hosted on injistackqa and
pinned to immutable version tags or digests (e.g.,
injistackqa/inji-certify-with-plugins:<version> or `@sha256`:<digest> and
injistackqa/apitest-inji-certify:<version> or `@sha256`:<digest>) so the release
manifest is reproducible and the registry migration is applied.
2 participants
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.