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

Webhook support for tags #4470

New Issue
Closed
opened 2025-12-29 18:36:20 +01:00 by adam · 9 comments
adam commented 2025-12-29 18:36:20 +01:00
Owner
Copy Link

Originally created by @djrodriguezp on GitHub (Jan 18, 2021).

Originally assigned to: @jeremystretch on GitHub.

Environment

  • Python version: 3.6.8
  • NetBox version: 2.10.3

Proposed Functionality

Add webhook support for tags creation, update or delete in GUI Organization > tags

Use Case

Notify via webhook to an external application anytime a tag is added, updated or deleted.

Database Changes

External Dependencies

Originally created by @djrodriguezp on GitHub (Jan 18, 2021). Originally assigned to: @jeremystretch on GitHub. <!-- NOTE: IF YOUR ISSUE DOES NOT FOLLOW THIS TEMPLATE, IT WILL BE CLOSED. This form is only for proposing specific new features or enhancements. If you have a general idea or question, please start a discussion instead: https://github.com/netbox-community/netbox/discussions NOTE: Due to an excessive backlog of feature requests, we are not currently accepting any proposals which significantly extend NetBox's feature scope. Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report. --> ### Environment * Python version: 3.6.8 * NetBox version: 2.10.3 <!-- Describe in detail the new functionality you are proposing. Include any specific changes to work flows, data models, or the user interface. --> ### Proposed Functionality Add webhook support for tags creation, update or delete in GUI **Organization > tags** <!-- Convey an example use case for your proposed feature. Write from the perspective of a NetBox user who would benefit from the proposed functionality and describe how. ---> ### Use Case Notify via webhook to an external application anytime a tag is added, updated or deleted. <!-- Note any changes to the database schema necessary to support the new feature. For example, does the proposal require adding a new model or field? (Not all new features require database changes.) ---> ### Database Changes <!-- List any new dependencies on external libraries or services that this new feature would introduce. For example, does the proposal require the installation of a new Python package? (Not all new features introduce new dependencies.) --> ### External Dependencies
adam added the status: acceptedtype: feature labels 2025-12-29 18:36:20 +01:00
adam closed this issue 2025-12-29 18:36:20 +01:00
adam commented 2025-12-29 18:36:21 +01:00
Author
Owner
Copy Link

@lampwins commented on GitHub (Jan 19, 2021):

There are a couple of other "extras" models that don't support webhooks today, like config contexts. If we were to do this (which I support), I think we should also do it for those other models for which it makes sense.

@lampwins commented on GitHub (Jan 19, 2021): There are a couple of other "extras" models that don't support webhooks today, like config contexts. If we were to do this (which I support), I think we should also do it for those other models for which it makes sense.
adam commented 2025-12-29 18:36:21 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 19, 2021):

Notify via webhook to an external application anytime a tag is added, updated or deleted.

That's the raw functionality this would enable, but what is your underlying use case?

@jeremystretch commented on GitHub (Jan 19, 2021): > Notify via webhook to an external application anytime a tag is added, updated or deleted. That's the raw functionality this would enable, but what is your underlying use case?
adam commented 2025-12-29 18:36:21 +01:00
Author
Owner
Copy Link

@sdktr commented on GitHub (Jan 19, 2021):

if a tag would change (it's name for example), should the related entities that point to this tag all get a change signal (webhook/last_change date update etc) as well?

@sdktr commented on GitHub (Jan 19, 2021): if a tag would change (it's name for example), should the related entities that point to this tag all get a change signal (webhook/last_change date update etc) as well?
adam commented 2025-12-29 18:36:21 +01:00
Author
Owner
Copy Link

@djrodriguezp commented on GitHub (Jan 19, 2021):

Notify via webhook to an external application anytime a tag is added, updated or deleted.

That's the raw functionality this would enable, but what is your underlying use case?

I need to create host templates based on tags in my network monitoring system via API that's why webhooks will be very useful.

@djrodriguezp commented on GitHub (Jan 19, 2021): > > Notify via webhook to an external application anytime a tag is added, updated or deleted. > > That's the raw functionality this would enable, but what is your underlying use case? I need to create host templates based on tags in my network monitoring system via API that's why webhooks will be very useful.
adam commented 2025-12-29 18:36:22 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 19, 2021):

But why would you need a webhook when a tag itself changes?

@jeremystretch commented on GitHub (Jan 19, 2021): But why would you need a webhook when a tag itself changes?
adam commented 2025-12-29 18:36:22 +01:00
Author
Owner
Copy Link

@djrodriguezp commented on GitHub (Jan 19, 2021):

But why would you need a webhook when a tag itself changes?

I was thinking this use case to rename the template when the Nerbox event is "updated" on the tag and create the template if the event is "created".

@djrodriguezp commented on GitHub (Jan 19, 2021): > But why would you need a webhook when a tag itself changes? I was thinking this use case to rename the template when the Nerbox event is "updated" on the tag and create the template if the event is "created".
adam commented 2025-12-29 18:36:22 +01:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Mar 5, 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.

@stale[bot] commented on GitHub (Mar 5, 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 18:36:22 +01:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Mar 21, 2021):

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.

@stale[bot] commented on GitHub (Mar 21, 2021): 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.
adam commented 2025-12-29 18:36:22 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 22, 2021):

IIRC this is covered under some of the v2.12 standardization work but I need to dig into it.

@jeremystretch commented on GitHub (Mar 22, 2021): IIRC this is covered under some of the v2.12 standardization work but I need to dig into it.
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 status: accepted 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#4470
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?