Skip to content

Move Introspection triggers into Device triggers #76

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

Merged

Conversation

Annopaolo
Copy link
Collaborator

@Annopaolo Annopaolo commented Sep 6, 2022

Introspection triggers are currently unused. In order to start keeping track of introspection changes, group them with the related device triggers. To be consistent with other triggers, make naming uniform (e.g. replace the match_interface field with the pair {interface_name, interface_major}).

Introspection triggers are currently unused. Move them in the device logic to start keeping track of introspection changes.

Signed-off-by: Arnaldo Cesco <[email protected]>
@Annopaolo Annopaolo marked this pull request as ready for review September 6, 2022 10:07
@Annopaolo Annopaolo added the API This issue or pull request is about API (e.g. unclear API, new API, API change, deprecation) label Sep 6, 2022
@Annopaolo Annopaolo requested review from rbino and bettio September 6, 2022 10:07
@codecov
Copy link

codecov bot commented Sep 6, 2022

Codecov Report

Merging #76 (0b82e33) into master (b345a87) will increase coverage by 0.22%.
The diff coverage is 88.88%.

❗ Current head 0b82e33 differs from pull request most recent head 2e1e092. Consider uploading reports for the commit 2e1e092 to get more accurate results

@@            Coverage Diff             @@
##           master      #76      +/-   ##
==========================================
+ Coverage   84.12%   84.34%   +0.22%     
==========================================
  Files          21       21              
  Lines         485      511      +26     
==========================================
+ Hits          408      431      +23     
- Misses         77       80       +3     
Impacted Files Coverage Δ
lib/astarte_core/triggers/simple_trigger_config.ex 95.62% <88.88%> (-1.68%) ⬇️

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

Annopaolo added a commit to Annopaolo/astarte that referenced this pull request Sep 6, 2022
Since introspection triggers are now device triggers, reflect this
change in related funcitons.
See astarte-platform/astarte_core#76.

Signed-off-by: Arnaldo Cesco <[email protected]>
@Annopaolo Annopaolo requested a review from Pavinati September 6, 2022 14:00
Annopaolo added a commit to Annopaolo/astarte that referenced this pull request Sep 6, 2022
Since introspection triggers are now device triggers, reflect this
change in related funcitons.
See astarte-platform/astarte_core#76.

Signed-off-by: Arnaldo Cesco <[email protected]>
@Annopaolo Annopaolo force-pushed the introspection-triggers-to-device branch from 60412a1 to ad05506 Compare September 12, 2022 09:15
Reconcile the introspection (device) triggers API with the one exposed by data triggers,
e.g. use the same name for equivalent fields, and allow either {interface_name, interface_major}
or any interface as match condition for interface added/removed/updated triggers.
@Annopaolo Annopaolo force-pushed the introspection-triggers-to-device branch from ad05506 to 2e1e092 Compare September 20, 2022 14:43
@Annopaolo Annopaolo requested a review from rbino September 20, 2022 15:10
@bettio bettio merged commit 150d0ce into astarte-platform:master Sep 21, 2022
Annopaolo added a commit to Annopaolo/astarte that referenced this pull request Sep 22, 2022
Since introspection triggers are now device triggers, reflect this
change in related funcitons.
See astarte-platform/astarte_core#76.

Signed-off-by: Arnaldo Cesco <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
API This issue or pull request is about API (e.g. unclear API, new API, API change, deprecation)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants