API issues

[oscgonfer]

API Issues (in order of priority)

Ingestion

• Shared subscription: Shared subscription in MQTT #355 and test coverage for it. Related: Review MQTT implementation for scalability #198
• Improvements on json parsing and validation: Non-existing sensors in device #326 and Add a means of tracking data parse errors for a device #288
• Forwarding should include http posts: Make sure forwarding also includes data from http batch posts #357 and additional Forwarding Checks #358

Quicky stuff

• Make precise_location true by default #359
• Null value should not be "null" but null? #354

Docs

• Update the API docs

Docker configuration

• Docker health-checks #363

Monolith

Discussion here: #183

Endpoints

• Privileges and actions review: Review priviledges and roles, is_private should be allowed for anyone #349
  • Review the cases first
• /V1:
  • System tags and exposure: Exposure is not a database column #282
  • Device representation: Improvements to forwarding #329
  • Single translator (POST/GET)
  • null values: Null value should not be "null" but null? #354
  • Consistency of data types: Improve consistency on data types for responses #334
  • Tags and searching: Multiple ransak filters in URL - with_tags ransak filter missing on documentation #186
  • Web-sockets removal rollback?

Forwarding Improvements

• Make forwarding in MQTT per topics
• Add forwarding not only per user, but per experiment?
  • Check first user roles. DDoS
• Add license field _somewhere_ #370

Security

• Token generation. Improve token generation for users #312

Bugs

• Review response codes #279 (low prio)

Low prio

• Minuteman: (Minuteman, removed). Do we need the readings info in /metrics endpoint? #100
• Git branch in API Add git hash and branch to version_git field in API #281
• Add tests for creating Tags #124

Potentially discarded

• Kafka and other clients:
  • Proposal: Migrating to Apache Kafka for Enhanced Data Processing and Reliability #265
  • Investigate moving to an alternative MQTT client #302
  • Device message serialization improvements #301