Astarte export: Add support for parametric interfaces #1041
+96
−9
Conversation
This file contains 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
Fetch endpoint paths for data mappings and update related processing logic. Closes astarte-platform#1028 Signed-off-by: Osman Hadzic <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What this PR does / why we need it:
Adds functionality to fetch endpoint paths for data mappings.
Updates the related processing logic to support the new fetched paths.
To ensure data mappings are dynamically handled based on the correct endpoint paths.
To improve the data processing logic's flexibility and accuracy, ensure it works with the updated endpoint paths.
Which issue(s) this PR fixes:
Closes #1028
Fixes #
Closes #1028
Special notes for your reviewer:
Fetching data from the table
individual_property. Aggregation object data is filtered usingdevice_idandinterface_id. The aggregation of individuals adds one more argument:endpoint_id.Does this PR introduce a user-facing change?
Additional documentation e.g. usage docs, diagrams, etc.: