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

Handle recursive resources within a device profile (command chaining) #3

Closed
iain-anderson opened this issue Sep 20, 2018 · 3 comments
Closed

Comments

@iain-anderson
Copy link
Member

Instead of containing a reference to a device resource (the device resource's name is in the "object" field), a resourceoperation may refer to other (profile) resources. In this case the "resource" field will be set to the name of the profile resource.

See the sample profile DENT.Mod.PS6037.profile.yaml in device-modbus for an example.

@iain-anderson iain-anderson changed the title Handle recursive resources within a device profile Handle recursive resources within a device profile (command chaining) Sep 20, 2018
@iain-anderson
Copy link
Member Author

This would be a good time to enhance the device profile reading code so that it resolves resource/deviceresource names when profiles are loaded.
IE, edgex_resourceoperation.object becomes an edgex_deviceresource*
and edgex_resourceoperation.resource becomes an edgex_profileresource*

@iain-anderson
Copy link
Member Author

Not happening for Geneva (was not committed in scope)

@iain-anderson
Copy link
Member Author

Agreed in Levski planning meeting that this would not be implemented. Note that the fields specifying nested device commands were removed in the profile rework for EdgeX 2.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant