fix issue with static attributes in the current tutorial requests #11
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The current tutorial requests have an issue that if you execute them one by one, the static attributes don't get included into the device entity in the context broker, which makes them not query-able.
This is mentioned in an issue on the iotagent-json repo: telefonicaid/iotagent-json#835.
The solution is to either set the service group
entity_typeto match theentity_typeof the device when provisioned (which is what I've done for now) or to also include the service'sapikeyfor the device when provisioning the device (which I've not included by now).