Retire API v1 ingest URLs (`/api/raw-packet/`, legacy node paths)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
Start with Meshflow/urls.py and packets.urls to confirm that only the {node_id}/ingest/ and {node_id}/nodes/ routes are registered, then search the tree for any remaining v1 view code tied to /api/raw-packet/. Check openapi.yaml for the deprecated POST /raw-packet/ entry and the docs under docs/features/packet-ingestion/. Done means no v1 routes or view code remain, the docs describe v2 only, and any compatibility redirect decision is recorded. The bot-side change and the production proxy question need maintainer input before merging.
Written by the indexing model from the issue text.
Description
Summary
Meshtastic packet ingest v1 used unscoped URLs (POST /api/raw-packet/, /api/nodes/) that predate the current packets app layout. v2 uses observer-scoped routes:
POST /api/packets/{node_id}/ingest/POST /api/packets/{node_id}/nodes/
OpenAPI now documents v2 paths and marks POST /raw-packet/ as deprecated (SP-01 #308). v1 is not registered in the current Django urlconf (Meshflow/urls.py → packets.urls only exposes {node_id}/ingest/ and {node_id}/nodes/).
Goal
Formally retire v1 on the API side and coordinate with meshflow-bot dropping STORAGE_API_VERSION=1 (see linked bot issue).
Scope (API)
- Confirm no production urlconf / reverse-proxy still depends on
/api/raw-packet/(or document explicit redirect shim if required during transition) - Remove or gate any dead v1 view code if it still exists in the tree
- Update operator docs (
docs/features/packet-ingestion/, deploy examples) to state v2-only - After bot default is v2 and operators migrated: remove deprecated
POST /raw-packet/fromopenapi.yaml(or keep stub only if a compat redirect remains)
Out of scope
- URL prefix rename
/api/packets/→/api/meshtastic/(meshcore rename SP-03+) - MeshCore ingest (
/api/meshcore/packets/ingest/)
Related
- Bot: pskillen/meshflow-bot#95
- OpenAPI alignment: #308 (SP-01)
- Dominant language
- Python
- Stars
- 1
- Forks
- 0
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 8
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from pskillen/meshflow-api
-
enhancement meshtastic-2.8
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
pskillen/meshflow-api#459 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 73/100
pskillen/meshflow-api#472 ·
Maintainers usually reply within 1 day
-
enhancement meshtastic-2.8
Difficulty 4/5 3-5 days Newbie friendliness 22/100
pskillen/meshflow-api#464 ·
Maintainers usually reply within 1 day
-
enhancement meshtastic-2.8
Difficulty 4/5 3-5 days Newbie friendliness 35/100
pskillen/meshflow-api#463 ·
Maintainers usually reply within 1 day
-
enhancement meshtastic-2.8
Difficulty 3/5 1-2 days Newbie friendliness 45/100
pskillen/meshflow-api#462 ·
Maintainers usually reply within 1 day
All issues in pskillen/meshflow-api
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
unionai-oss/pandera#2640 ·
Maintainers usually reply within 2 days
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
JdeRobot/RoboticsInfrastructure#843 ·
Maintainers usually reply within 1 day
-
automated endpoint-dead needs-curation
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
almanac-data/climate-almanac#122 ·
Maintainers usually reply within 1 day
-
area:harness enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
evarness-ai/iris-harness#420 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
suitenumerique/find#206 ·
Maintainers usually reply within 2 days