You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sorry, it seems "interrupting" is a wrong word to describe what I meant here.
It should be more like skipping of triggering web hook remote url, without actual interrupting of flow.
E.g. a remote url is triggered only for specific schemas, while for the others a web hook will be just skipped without an error or interrupting of the flow.
I'll update the description of the issue.
renom
changed the title
Interrupting flow from web hook jsonnet
Jsonnet flag to skip triggering of web hook
Sep 30, 2024
Preflight checklist
Ory Network Project
No response
Describe your problem
Our project needs to run a web hook for a specific identity schema only.
Describe your ideal solution
Setting a specific key in jsonnet to skip triggering of the web hook, for example:
Then the web hook will be skipped if schema_id isn't "specific_schema_id".
Workarounds or alternatives
Alternative solution would be adding a list of allowed schemas to web hook config:
- hook: web_hook config: url: <web_hook_url> method: POST body: request-data.jsonnet + allowed_schemas: ["schema_id_1", "schema_id_2", ...]
Version
1.3.0
Additional Context
No response
The text was updated successfully, but these errors were encountered: