-
Notifications
You must be signed in to change notification settings - Fork 42
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
Comments
This would be a good time to enhance the device profile reading code so that it resolves resource/deviceresource names when profiles are loaded. |
Not happening for Geneva (was not committed in scope) |
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 |
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.
The text was updated successfully, but these errors were encountered: