Show whether a feeder is registered vs. claimed in the UI#59
Merged
Conversation
Adds GET /api/claim/status, backed by a single-flight, identity-keyed cache over a read-only `apl-feed claim status` probe, and replaces the claim activity panel's secret-presence guess with the real registered-vs-claimed verdict, a freshness stamp, and a Check now button.
A colored dot + label in the Identity card header reflects the /api/claim/status verdict — green claimed, blue registered, orange not registered, red action needed, grey unknown — refreshed on dashboard load and the status-snapshot poll.
readsb is the local decoder every other 1090 tile depends on; surfacing it first matches the data path (decode → feed → mlat).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The feeder web UI's claim activity view previously labelled any feeder that had a local claim secret as "Claimed ✓" — even when no account had actually claimed it. It now reports the real state from the backend: not registered, registered but not yet claimed, or claimed.
A new
GET /api/claim/statusendpoint readsapl-feed claim statusand caches the result server-side with a single-flight guard, so reloads and multiple tabs collapse to a single backend check. The view re-checks on a slow cadence only while a claim is still pending and stops once the state is settled, with a "Check now" button to force a refresh. The webconfig itself makes no network calls — it shells out to the feed CLI as the unprivileged service user.