python-azure-iot-edge-modules

Define the module's inputs, outputs, and message schema first, then package it as a container image with a pinned Python runtime and resource limits. This Skill guides the full workflow from contract definition through deployment manifests and validation testing.

Implement retries with exponential backoff and jitter, use local queueing for upstream failures, and design idempotent handlers for replayed messages. The Skill also requires graceful degradation and bounded timeouts to keep the edge device stable.

A deployment manifest should define module images, environment variables, routes, and desired properties per environment. It must never contain plaintext secrets, and should be paired with rollout stages, rollback criteria, and alerting conditions.

Yes, protocol adapter modules converting serial, Modbus, or OPC-UA data to IoT message format are a listed use case. The Skill covers message schema versioning, routing priorities, and validation for such translation workloads.

The Skill prohibits direct production rollout without a pilot stage and requires health probes, restart behavior, and rollback criteria in every plan. It also depends on reviewing current Microsoft IoT Edge documentation, flagging assumptions when docs cannot be fetched.