starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-13 13:53:31 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

enable webhook on export event #5488

New Issue
Closed
opened 2025-12-29 19:28:36 +01:00 by adam · 4 comments
adam commented 2025-12-29 19:28:36 +01:00
Owner
Copy Link

Originally created by @gstorme on GitHub (Oct 7, 2021).

NetBox version

v3.0.6

Feature type

Change to existing functionality

Proposed functionality

Would it be possible to enable a webhook on "Export" events?

Use case

Be notified, or take any action, whenever an export is taken.

Database changes

No response

External dependencies

No response

Originally created by @gstorme on GitHub (Oct 7, 2021). ### NetBox version v3.0.6 ### Feature type Change to existing functionality ### Proposed functionality Would it be possible to enable a webhook on "Export" events? ### Use case Be notified, or take any action, whenever an export is taken. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurepending closurestatus: under review labels 2025-12-29 19:28:36 +01:00
adam closed this issue 2025-12-29 19:28:37 +01:00
adam commented 2025-12-29 19:28:38 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 7, 2021):

It's an interesting idea, though IMO it doesn't quite fit the webhook feature. Webhooks were intended to notify on changes to object state, and merely exporting objects isn't a state change. It would also be very hard to define a substantial distinction between exporting via an export template and retrieving objects via the REST API.

That's not to say there aren't other potential solutions though. Could you elaborate a bit on your use case? What exactly are you wanting to accomplish?

@jeremystretch commented on GitHub (Oct 7, 2021): It's an interesting idea, though IMO it doesn't quite fit the webhook feature. Webhooks were intended to notify on changes to object state, and merely exporting objects isn't a state change. It would also be very hard to define a substantial distinction between exporting via an export template and retrieving objects via the REST API. That's not to say there aren't other potential solutions though. Could you elaborate a bit on your use case? What exactly are you wanting to accomplish?
adam commented 2025-12-29 19:28:38 +01:00
Author
Owner
Copy Link

@gstorme commented on GitHub (Oct 8, 2021):

I'd like to send a slack alert whenever someone takes an export, with the logged in username and which data type was exported in the body (ipam/aggregates, dcim/devices,...).

@gstorme commented on GitHub (Oct 8, 2021): I'd like to send a slack alert whenever someone takes an export, with the logged in username and which data type was exported in the body (ipam/aggregates, dcim/devices,...).
adam commented 2025-12-29 19:28:38 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Dec 8, 2021):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Dec 8, 2021): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 19:28:38 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jan 7, 2022):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Jan 7, 2022): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label pending closure status: under review type: feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#5488
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?