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
-> Easy update of the autonomous system on RIPE IRR with a push of a button when peering connections are updated.
-> Before syncing, they can inspect the rendered body for validation.
-> Users can have multiple maintainers on RIPE IRR.
Use case
-> Saving time
-> Less error-prone
-> Easy to use
Database changes
-> New model to store passwords
External dependencies
No response
The text was updated successfully, but these errors were encountered:
The export template feature introduced in 1.7.0 can help in solving this issue. It still lacks the export to URL (or whatever) feature. So I'll leave this issue open, and update its title to better match the current missing bits.
gmazoyer
changed the title
Update autonomous system on RIPE IRR easier
Allow export template to be sent to a URL
Aug 21, 2022
Just came across this. This would indeed be a very nice feature to have. IRR aut-num objects notoriously get out of sync with real-world peerings, so having this integrated would do wonders for data quality :-)
I would propose to have a new django-admin command that would render a template and send it somewhere as a HTTP POST.
For this, the template would have to render to a JSON document containing the URL, headers and body for the request.
One could then have a systemd-timer (or other way of automatic execution) to render and send the template whenever they need to.
This may be adaptable to write the output to a local file instead.
I think the best way to tackle this would be to leverage the code that has been written for the webhook feature. With a bit of rework, I think we could implement this.
Peering Manager version
v1.5.3-dev
Feature type
New functionality
Proposed functionality
-> Easy update of the autonomous system on RIPE IRR with a push of a button when peering connections are updated.
-> Before syncing, they can inspect the rendered body for validation.
-> Users can have multiple maintainers on RIPE IRR.
Use case
-> Saving time
-> Less error-prone
-> Easy to use
Database changes
-> New model to store passwords
External dependencies
No response
The text was updated successfully, but these errors were encountered: