telefonicaid / telefonicaid/iotagent-node-lib
better management of device registration failure on orion
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 62
- Forks
- 90
- Avg merge
- 2h 35m
- Merged PRs (30d)
- 1
Description
As of today if orion returns 400 during registration, the registration fails. This means that the configuration data of the device are deleted, and you have to provide them again. While if you are just shutting API calls, that's not much a problem, UI users may find annoying that the configuration is not persisted despite the error.
To handle the situation, it could be nice to have in the device a field status which in case of errors is updated with proper code errors. @fgalan @jason-fox @AlvaroVega feelings?
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by tracing the device registration flow and the handling of Orion HTTP 400 responses. Determine where configuration data is deleted and how a device could retain it while recording an appropriate error status. Done means failed registration preserves the device configuration and exposes the relevant error status for UI users.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100