telefonicaid / telefonicaid/iotagent-node-lib

Homogenous way of setting poll commands in provisioning API

Open
#575 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
JavaScript
Stars
62
Forks
90
Avg merge
2h 35m
Merged PRs (30d)
1

Description

Currently, the mechanism to activate poll commands depends on the particular implementation of the IOTA using the library, as told in the README.md:

The distinction between push and poll commands will be made based on the presence of a polling flag in the device provisioning data. The details on how this flag is derived for provisioning data would depend on the particular IOT Agent implementation using this libray (in other words, there isn't any standard way of doing so). The default option (with the flag with value false or not present) is to use push commands (as they were the only ones available until the latest versions).

It would be great to have an homogenous mechanism for all agents, part of the provisioning API provided by the library. For example, a mode field for commands to state either poll or push.

Of course, the fragment of documentation above should be adjusted if this issue gets finally implemented.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the provisioning API and the push/poll command discussion in README.md. Determine how provisioning data currently carries the polling flag across IOT Agent implementations. Done means a homogeneous command mode for poll or push is supported by the API and the README description is updated accordingly.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
api, backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.