Breaking action chain in a before_action?
Problem Statement:
My webhook receives at-least-once messaging from an external producer, and I want to persist these Events -- ids generated by the producer-- as an Ash Resource, such that only one instance is saved in the database (postgres), and an Oban job is only enqueued once.
I've created a custom
Issue:
However, it doesn't look like there is any information in the
Possible solutions?
1. Add a
2. Or, probably better, is if there a way for a
My webhook receives at-least-once messaging from an external producer, and I want to persist these Events -- ids generated by the producer-- as an Ash Resource, such that only one instance is saved in the database (postgres), and an Oban job is only enqueued once.
I've created a custom
:addupsert?Issue:
However, it doesn't look like there is any information in the
Ash.Changeset.after_actionPossible solutions?
1. Add a
nonce2. Or, probably better, is if there a way for a
before_actionaround_action
The Elixir backend framework for unparalleled productivity. Declarative tools that let you stop wasting time. Use with Phoenix LiveView or build APIs in minutes for your front-end of choice.
2,193Members
Resources
Similar Threads
Was this page helpful?
