+33
−0
+153
−0
Loading
POST /operatorplatform/federation/v1/{federationContextId}/
application/lcm with an Idempotency-Key: authenticate the partner,
resolve their inbound context, check the agreement permits
install-app in that zone, resolve the app triple to a service
specification, persist a pending transaction, publish
command.srm.service.deploy, flip to in_progress and answer 202 with
the zone and a new instance identifier.
Replaying the same key returns the same instance without
republishing; the same key with a different body is a 409
(idempotency-key-reused). Nothing is published when authorisation
fails. The instance identifier is a UUID's hex form because GSMA's
InstanceIdentifier pattern forbids dashes; zone ids parse as UUIDs
per ADR-0017, so a non-UUID zone is an agreement violation.
The SRM command envelope is extra="forbid" (validated against the
SRM pydantic model on feat/location-retrieval-api), so fields must
never be added to it. FM now requires NATS at startup.