cms-demo-case

What problem does it solve?

Manually patching CMS NPE cases with the specific demo values required for TDFS, LEAPI, and LRMS workflows is time-consuming and error-prone, especially when dealing with constraints like server-managed identifierHash fields that require direct Cosmos database access.

Core Features & Use Cases

• Idempotent Demo Case Patching: Safely patch LNS CMS cases with required demo fields (regionDataCenter, publishChannel, start/endDateTime, identifierHash) without risk of duplicate or conflicting updates.
• Secure ACI-Based Execution: Runs all patch operations inside an Azure Container Instance deployed in the NPE VNet, using the correct UAMI authentication for both the CMS API and Cosmos data plane.
• Built-In Validation & Safety: Includes dry-run mode to preview changes before mutation, automatic handling of common edge cases (case ID format errors, tenant misconfiguration, PIM permission decay), and idempotent re-runs that are safe to execute multiple times. Use case: For engineering teams preparing TDFS, LEAPI, or LRMS demos, use this skill to quickly configure all required demo case fields in the NPE CMS environment without manual API calls or risk of corrupting data.

Quick Start

Use the cms-demo-case skill to patch the LNS case LNS-1778014194-AR3RSD26 with all required demo values for downstream TDFS, LEAPI, and LRMS testing.