Implement UC-FM-01: terminate a federated application instance (RemoveApp)

Sergio Gimenezrequested to merge
feat/uc-fm-01-remove-app into develop

Completes UC-FM-01 (Inbound Federated Deployment) and Foundation #4 (closed) in the delivery plan, which asks for inbound deploy and terminate. Deploy landed earlier; this is the other half.

What a partner can now do

Having deployed an app with us, a partner can take it down:

DELETE /operatorplatform/federation/v1/{federationContextId}
       /application/lcm/app/{appId}/instance/{appInstanceId}/zone/{zoneId}

FM authenticates the partner, resolves their federation context, finds the deployment that minted that appInstanceId, writes a new federation_transactions row, publishes command.srm.service.terminate, and answers 200. SRM's completion event finalises the row through the consumer that already exists, so no new event handling was needed.

Known Limits

  • Not verified against a live SRM. SRM's command.srm.service.terminate handler is still a no-op on origin/feat/location-retrieval-api, so nothing acts on the command and no completion event comes back. FM's side is complete and the loop will close when SRM implements it.
  • No partner callback on termination. The onInstanceStatusEvent callback fires from the completion event, which SRM does not yet emit for terminate. The callback URL is carried on the new row so it works unchanged once it does.

Merge request reports