Setting static attribute values when creating a new device is painful

[giovannicuriel]

• I'm submitting a ...

  • [ ] bug report
  • [x] feature request
  • [ ] support request

• Do you want to request a feature or report a bug? Feature

• What is the current behavior? DeviceManager needs the attribute ID from a template when setting a static attribute from a new device. This absolutely makes no sense - there is already a verification to check whether there is no conflict between template attribute names, so what's the point of having its attribute ID as well? This is certain to create problems and confusion when creating devices via API.

• If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem

• What is the expected behavior?

• What is the motivation / use case for changing the behavior?

• Please tell us about your environment:

  • Version: 0.2.x
  • Environment: [kubernetes, docker-compose, standalone]
  • Operating system: [Ubuntu 16.04, Fedora 28, Ubuntu on VirtualBox (Windows 10), etc.]

• Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)