Add 'apl-feed claim status' to report account-claim state#125
Merged
Conversation
Distinguishes a feeder registered with the backend from one claimed by a user account (owner_present), via a read-only /api/feeders/status probe. A shared http.sh helper unifies response parsing with apl-feed status. Emits schema-v1 JSON or a human summary; writes nothing, so it runs unprivileged.
d4rken
force-pushed
the
feat/apl-feed-claim-status
branch
from
c13cf4c to
9e9d282
Compare
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.
Adds
apl-feed claim status— a read-only command that reports whether a feeder is registered with airplanes.live and whether a user account has actually claimed it. It probes the feeder-status endpoint with the local claim secret and prints a short human summary, or a stable machine-readable object with--json.The command writes nothing and needs no elevated privileges, so on-device tooling can call it directly. Response parsing is shared with
apl-feed statusso the two stay consistent on the wire shape.