-
Notifications
You must be signed in to change notification settings - Fork 47
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
Start SSOT job based on IP Fabric Webhook #194
Comments
You can trigger Jobs via API: https://nautobot.readthedocs.io/en/stable/additional-features/jobs/#via-the-api |
Unfortunately no as IP Fabric does not let you send custom responses. The endpoint receiving the webhooks must parse the data and then do automation against it. https://ipfabric.atlassian.net/wiki/spaces/ND/pages/1456537601/Webhooks |
So, if don't understand it wrong, the problem is that you can't add "data" or custom authorization to the request. |
Nautobot will need to process the webhook IP Fabric sends because it sends a message for every discovery action and status: This will then possibly kick off an SSOT job for example when a snapshot action:delete/status:started which is incorrect. It needs to only kick off an SSOT job when action:discover, status:completed, requester:cron. There is no way to add any authorization to the webhook. Nautobot will need to accept the event and verify the message: Full IP Fabric webhook message: |
Just for kicks, worth exploring the roadmap of webhooks in IPF too. For example, being able to template the JSON body as in Nautobot make it very flexible! :) https://nautobot.readthedocs.io/en/latest/models/extras/webhook/#jinja2-template-support |
At this time changes to IP Fabric webhooks is not on the roadmap as our highest priorities is adding new vendor functionality. |
Environment
Proposed Functionality
IP Fabric allows for webhooks to send to external systems when discovery completes. It would be nice to have IPF send the webhook to Nautobot and that it automatically runs the SSOT job.
Use Case
The text was updated successfully, but these errors were encountered: