Challenge: fix a batch job and ship a private multi-container API on ACI

تحدي: صلّح Batch job وانشر API خاص فيه أكتر من Container على ACI

In rg-x4-ch-aci the nightly job etl-job finishes its work in seconds, yet the bill shows it running all day and its restart count keeps climbing. The platform team also needs an internal API on ACI that only workloads in vnet-int can reach (client VM vm-client in snet-apps ; empty subnet snet-aci ), writing its uploads to the file share ingest in storage account stx4chaci01 . Meet the requirements with any tool.

The 4 tasks you will do

• Requirement 1 — The batch job runs once and stops billingالمتطلب 1 — الـ Batch job يشتغل مرة ويوقف الحساب
• Requirement 2 — Keep a definition in source control without leaking the tokenالمتطلب 2 — احفظ التعريف في الـ Source control من غير ما يتسرّب الـ Token
• Requirement 3 — Private two-container API with persistent storageالمتطلب 3 — API خاص فيه اتنين Containers وتخزين دايم
• Requirement 4 — Prove reachability and persistenceالمتطلب 4 — اثبت إن الوصول والتخزين شغالين

The lesson it belongs to

• Azure Container Instances in depth: container groups, volumes, secrets, restart policies and VNet deployment