Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Check duplicities in attribute names #81

Open
dmoranj opened this issue May 6, 2015 · 0 comments
Open

Check duplicities in attribute names #81

dmoranj opened this issue May 6, 2015 · 0 comments

Comments

@dmoranj
Copy link
Contributor

dmoranj commented May 6, 2015

Currently, the IoT Agent doesn't make any duplicity checks on the names that are provisioned via the Device Provisioning API or the Configuration API. The following checks should be done in each incoming creation or update:

  • In a Device provisioning, each attribute name in the active, lazy, static or command category arrays must be unique among all the categories.
  • In a Configuration provisioning, each attribute name in the active, lazy, static or command category arrays must be unique among all the categories.
  • If a Device belonging to a Configuration is provisioned, and an attribute in any of the attribute categories (e.g: lazy) is defined in that provision, its name should not be present in any other category (e.g: active or command). I.e: a lazy attribute in the device should be able to overwrite a lazy attribute in the Configuration, but should not conflict with attributes in the active, command or static categories.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant