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

Add Config Context change tracking #2933

New Issue
Closed
opened 2025-12-29 18:23:43 +01:00 by adam · 4 comments
adam commented 2025-12-29 18:23:43 +01:00
Owner
Copy Link

Originally created by @leec-666 on GitHub (Oct 8, 2019).

Environment

  • Python version: 3.5.1-3
  • NetBox version: 2.6.5

Proposed Functionality

Config Context change tracking

Use Case

Config Context change tracking would allow for external versioning and review.

If an automation tool is using this information to fill templates and configure devices, you'd want to ensure that the stored information is correct. Whilst you could do this by hand, when you're dealing with tens+ of config context objects, it would quickly become tedious and you could still miss small, subtle changes to the text content.

Database Changes

Unknown

External Dependencies

Unknown

Originally created by @leec-666 on GitHub (Oct 8, 2019). <!-- NOTE: This form is only for proposing specific new features or enhancements. If you have a general idea or question, please post to our mailing list instead of opening an issue: https://groups.google.com/forum/#!forum/netbox-discuss 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.5.1-3 * NetBox version: 2.6.5 <!-- Describe in detail the new functionality you are proposing. Include any specific changes to work flows, data models, or the user interface. --> ### Proposed Functionality Config Context change tracking <!-- 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 Config Context change tracking would allow for external versioning and review. If an automation tool is using this information to fill templates and configure devices, you'd want to ensure that the stored information is correct. Whilst you could do this by hand, when you're dealing with tens+ of config context objects, it would quickly become tedious and you could still miss small, subtle changes to the text content. <!-- 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 Unknown <!-- 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 Unknown
adam added the status: acceptedtype: feature labels 2025-12-29 18:23:43 +01:00
adam closed this issue 2025-12-29 18:23:43 +01:00
adam commented 2025-12-29 18:23:43 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 17, 2019):

Add Config Context change tracking + webhooks

These would be two separate feature requests. I'm going to edit this issue so that it applies only to the change logging ability. Feel free to open up a separate FR for the webhook portion, however I don't think it makes sense to enable webhooks for ConfigContexts as they are not "real" objects: A device or VM may receive an arbitrary combination of data from various ConfigContexts depending on how they are applied.

@jeremystretch commented on GitHub (Oct 17, 2019): > Add Config Context change tracking + webhooks These would be two separate feature requests. I'm going to edit this issue so that it applies only to the change logging ability. Feel free to open up a separate FR for the webhook portion, however I don't think it makes sense to enable webhooks for ConfigContexts as they are not "real" objects: A device or VM may receive an arbitrary combination of data from various ConfigContexts depending on how they are applied.
adam commented 2025-12-29 18:23:43 +01:00
Author
Owner
Copy Link

@sdktr commented on GitHub (Oct 25, 2019):

Interesting to know whether a change in a configcontext currently triggers a webhook for the indirectly (eg via site) attached entities🧐

@sdktr commented on GitHub (Oct 25, 2019): Interesting to know whether a change in a configcontext currently triggers a webhook for the indirectly (eg via site) attached entities🧐
adam commented 2025-12-29 18:23:44 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 26, 2019):

@sdktr No, it doesn't. Only direct changes to an object will trigger an associated webhook.

@jeremystretch commented on GitHub (Nov 26, 2019): @sdktr No, it doesn't. Only direct changes to an object will trigger an associated webhook.
adam commented 2025-12-29 18:23:44 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 24, 2020):

This was implemented in v2.9 under #4840. My mistake; I hadn't realized there was already an issue open for this.

@jeremystretch commented on GitHub (Jul 24, 2020): This was implemented in v2.9 under #4840. My mistake; I hadn't realized there was already an issue open for this.
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#2933
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?