-
Notifications
You must be signed in to change notification settings - Fork 49
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
Gghio/692/trigger name events #923
Merged
Annopaolo
merged 3 commits into
astarte-platform:master
from
shinnokdisengir:gghio/692/trigger-name-events
Apr 17, 2024
Merged
Gghio/692/trigger name events #923
Annopaolo
merged 3 commits into
astarte-platform:master
from
shinnokdisengir:gghio/692/trigger-name-events
Apr 17, 2024
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
Annopaolo
requested changes
Apr 12, 2024
apps/astarte_trigger_engine/lib/astarte_trigger_engine/events_consumer.ex
Outdated
Show resolved
Hide resolved
apps/astarte_trigger_engine/lib/astarte_trigger_engine/events_consumer.ex
Outdated
Show resolved
Hide resolved
apps/astarte_appengine_api/lib/astarte_appengine_api/rpc/data_updater_plant.ex
Outdated
Show resolved
Hide resolved
shinnokdisengir
force-pushed
the
gghio/692/trigger-name-events
branch
5 times, most recently
from
April 12, 2024 16:00
8e60a64
to
4f06994
Compare
Annopaolo
requested changes
Apr 17, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, just a fix in the doc
Changed - send_simple_event - retrieve_trigger_configuration to integrate trigger_name inside payload FIX astarte-platform#692 Signed-off-by: Gabriele Ghio <gabriele.ghio@secomind.com>
Added trigger_name config information Signed-off-by: Gabriele Ghio <gabriele.ghio@secomind.com>
Signed-off-by: Gabriele Ghio <gabriele.ghio@secomind.com>
shinnokdisengir
force-pushed
the
gghio/692/trigger-name-events
branch
from
April 17, 2024 15:29
4f06994
to
296e96a
Compare
Annopaolo
approved these changes
Apr 17, 2024
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.
astarte_trigger_engine: add
trigger_name
to http eventRelative to #692
Currently, when a Trigger delivers an Event, the Event does not contain any information about the Trigger that generated it. This means that to distinguish between two triggers on the same interface, users have to use some out of band mechanism (e.g. using a different URL or adding a fixed query parameter).
trigger_name
both in mustache template and event payloadNo tests in this PR (there aren't tests for event data validation)