Skip to content

Import regional MeshMapper scope catalogues with durable cached fallback #173

Description

@n30nex

Implement the optional regional catalogue importer described in the shared scope plan, now that the public MeshMapper scopes API is available.

This first slice should preserve manual scopes and historical identities, validate explicit configured IATA sources, refresh with ETag/Retry-After and bounded requests, retain durable last-known-good membership through outages/restarts, and update the existing in-memory matcher without remote calls during ingest. Imported names alone must not create observer/node/traffic evidence. Group responses cannot be assigned to each member IATA.

Operator logs should report source, freshness and refresh status. Validate real PostgreSQL persistence, HTTP failures/304/empty snapshots, manual collisions, packet matching and bounded matching cost on the Pi. Channel scope tags and regional UI remain separate follow-ups. The feature is opt-in; existing preview candidates and rollback are retained. This continues the contributor's approved scope integration work; owners retain merges and release.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions