feat(fm): expose our federation identity on GET /internal/identity

Sergio Gimenezrequested to merge
feat/internal-identity into develop

feat/internal-identity → develop Title: feat(fm): expose our federation identity on GET /internal/identity

The portal must send partnerStatusLink in CreateFederation, but FM rejects any value other than its own configured one (400 federation-identity-mismatch), so the operator cannot type it. This serves the identity FM already builds from config (get_local_operator()), so OEG can relay it and the portal fills the field itself.

sequenceDiagram
    participant P as Portal
    participant OEG as OEG
    participant FM as FM
    P->>OEG: GET /platform/v1/federation/identity (role operator)
    OEG->>FM: GET /internal/identity
    FM-->>OEG: 200 {federation_id, country_code, mobile_network_codes, platform_caps, partner_status_link, instance_status_link, avail_zone_notif_link}
    OEG-->>P: relayed unchanged
  • Read-only, from config, no DB.
  • Like every /internal/* route today it has no authentication; it gets the federation-admin role once FM internal API auth lands (ADR-0064, proposed).
  • OEG side:

Tests: tests/test_internal_identity.py.

Merge request reports