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

Azure update time is common for all repositoryGroup #23

Open
2 of 4 tasks
mpostol opened this issue Aug 6, 2020 · 1 comment
Open
2 of 4 tasks

Azure update time is common for all repositoryGroup #23

mpostol opened this issue Aug 6, 2020 · 1 comment
Assignees
Labels
bug Something isn't working enhancement New feature or request

Comments

@mpostol
Copy link
Collaborator

mpostol commented Aug 6, 2020

repositoryGroup is a collection of variables that are used to create an Azure device. The following problems must be distinguished:

  • there are hardcoded update time for all repositoryGroup - in production environment it is useless
  • there is mopping between the class representing selected repositoryGroup and device capabilities model used by Azure.
  • the solution simulates a set of parallel independent devices connected to Azure - consider implementing it as a real gateway.
  • cannot find a possibility to read the communication parameters from the application configuration.
@mpostol mpostol added bug Something isn't working enhancement New feature or request labels Aug 6, 2020
@Drutol
Copy link
Owner

Drutol commented Aug 24, 2020

  1. Has been resolved in 56441ee
  2. Now configuration in connection with DTDL model provide the mapping based on common property names
  3. That'd be good option indeed but we lack proper documentation on implementing such devices.
  4. You can find these on the bottom of https://github.com/Drutol/CrossHMI/blob/master/CrossHMI/CrossHMI.AzureGatewayService/Configuration/LibraryConfigurationExample.json#L726

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants