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

config-templates api, bulk edit & view forms are missing the ``auto_sync_enabled`` property #11842

New Issue
Closed
opened 2025-12-29 21:50:32 +01:00 by adam · 4 comments
adam commented 2025-12-29 21:50:32 +01:00
Owner
Copy Link

Originally created by @ifoughal on GitHub (Nov 18, 2025).

Originally assigned to: @ifoughal on GitHub.

NetBox version

v4.4.6

Feature type

Data model extension

Proposed functionality

add the already available auto_sync_enabled property to the API, bulk edit & view forms.

This property allows the auto sync of the config-template when linked to a data-source, so that when the data-source is pulled, the changes are directly reflected onto the config-template.

Use case

  • create a data-source for a config template.
  • create a config-template linked to the data-source file via the file name field.
  • setting the ````auto_sync_enabled``` field to true is only available for this newly created config-template object.

bulk edits, or api create/update methods do not currently support this field.
the config-template view doesn't show this field neither, so the user would have to hit edit current object in order to check its value.

Database changes

No response

External dependencies

No response

Originally created by @ifoughal on GitHub (Nov 18, 2025). Originally assigned to: @ifoughal on GitHub. ### NetBox version v4.4.6 ### Feature type Data model extension ### Proposed functionality add the already available ```auto_sync_enabled``` property to the API, bulk edit & view forms. This property allows the auto sync of the config-template when linked to a data-source, so that when the data-source is pulled, the changes are directly reflected onto the config-template. ### Use case - create a data-source for a config template. - create a config-template linked to the data-source file via the file name field. - setting the ````auto_sync_enabled``` field to true is only available for this newly created config-template object. bulk edits, or api create/update methods do not currently support this field. the config-template view doesn't show this field neither, so the user would have to hit edit current object in order to check its value. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: bugstatus: acceptednetboxseverity: medium labels 2025-12-29 21:50:32 +01:00
adam closed this issue 2025-12-29 21:50:32 +01:00
adam commented 2025-12-29 21:50:35 +01:00
Author
Owner
Copy Link

@ifoughal commented on GitHub (Nov 18, 2025):

Hi, please assigne this issue to me, as I'm already working on this FR/fix.

@ifoughal commented on GitHub (Nov 18, 2025): Hi, please assigne this issue to me, as I'm already working on this FR/fix.
adam commented 2025-12-29 21:50:35 +01:00
Author
Owner
Copy Link

@ifoughal commented on GitHub (Nov 19, 2025):

my fix branch is ready to be merged.

@ifoughal commented on GitHub (Nov 19, 2025): my fix branch is ready to be merged.
adam commented 2025-12-29 21:50:36 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 19, 2025):

@ifoughal every issue needs to be triaged and evaluated by a maintainer before it will be approved for work. We recommend not beginning work on a feature request until it has been approved. Sometimes we opt to reject a feature request for various reasons, and work already undertaken will have been wasted.

@jeremystretch commented on GitHub (Nov 19, 2025): @ifoughal every issue needs to be triaged and evaluated by a maintainer before it will be approved for work. We recommend not beginning work on a feature request until it has been approved. Sometimes we opt to reject a feature request for various reasons, and work already undertaken will have been wasted.
adam commented 2025-12-29 21:50:36 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 20, 2025):

Reclassifying this as a bug and assigning to you @ifoughal. Thanks!

@jeremystretch commented on GitHub (Nov 20, 2025): Reclassifying this as a bug and assigning to you @ifoughal. Thanks!
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 netbox severity: medium status: accepted type: bug
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#11842
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?