docs+feat: Image transfer KT and single approval-based workflow

[Ivanmeneges]

Summary

Docs + workflow design for image transfer KT, handover, and approval-based transfer in a single YAML (no per-hop workflow files required).

Approval model (what you asked)

Yes — one workflow is enough. Multiple YAMLs are optional UX, not a security need.

Updated .github/workflows/image-transfer.yml:

• Input TRANSFER_TARGET (choice) = GitHub Environment name
• Job waits on environment: ${{ inputs.TRANSFER_TARGET }} for Approve/Reject
• Destination org is derived from the target (not free-typed)
• Uses Environment secret DOCKER_TOKEN (same name, different value per Environment)

Removed earlier image-transfer-dev2.yml / image-transfer-qa.yml examples.

Changes needed to go live (UI + process)

1. Create Environments: transfer-dev2, transfer-qa, transfer-mosipint, transfer-mosipid, Inji targets…
2. Per Environment: required reviewers + prevent self-review + secret DOCKER_TOKEN
3. Merge this workflow; operators pick TRANSFER_TARGET after images.txt PR merge
4. Remove old repo-level MOSIP*_DOCKER_TOKEN once gates work

Guide: release/docs/image-transfer-approval-single-workflow.md

Also in this PR

• Image transfer KT with merged-PR scenarios
• Handover plan / Environments how-to / WG approval test guide
• Vidivi README updated for new inputs

Note: Environments/secrets must be created in GitHub UI by a repo admin before the approval wait works.

  

[coderabbitai]

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

• Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

---

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