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

The sync permission for Data Source is not documented #8068

New Issue
Closed
opened 2025-12-29 20:31:54 +01:00 by adam · 5 comments
adam commented 2025-12-29 20:31:54 +01:00
Owner
Copy Link

Originally created by @kkthxbye-code on GitHub (May 16, 2023).

Originally assigned to: @jeremystretch on GitHub.

Change Type

Addition

Area

Integrations/API

Proposed Changes

I was unable to find any documentation of the required permission to sync a data source. Looking at the code, the additional action sync is needed for the Data Source object permission.

Originally created by @kkthxbye-code on GitHub (May 16, 2023). Originally assigned to: @jeremystretch on GitHub. ### Change Type Addition ### Area Integrations/API ### Proposed Changes I was unable to find any documentation of the required permission to sync a data source. Looking at the code, the additional action `sync` is needed for the `Data Source` object permission.
adam added the status: acceptedtype: documentation labels 2025-12-29 20:31:54 +01:00
adam closed this issue 2025-12-29 20:31:55 +01:00
adam commented 2025-12-29 20:31:55 +01:00
Author
Owner
Copy Link

@hhopjh commented on GitHub (Aug 14, 2023):

Any chance to fix this? At this point the only way to grant user permission to sync the Data Source is grant the user Super Admin right.

@hhopjh commented on GitHub (Aug 14, 2023): Any chance to fix this? At this point the only way to grant user permission to sync the Data Source is grant the user Super Admin right.
adam commented 2025-12-29 20:31:56 +01:00
Author
Owner
Copy Link

@kkthxbye-code commented on GitHub (Aug 14, 2023):

At this point the only way to grant user permission to sync the Data Source is grant the user Super Admin right.

No, this is only a documentation change. As is stated, the user just need to have the sync additional action assigned for the Data Store object permission. The issue is that is is not documented, but it should work fine.

@kkthxbye-code commented on GitHub (Aug 14, 2023): > At this point the only way to grant user permission to sync the Data Source is grant the user Super Admin right. No, this is only a documentation change. As is stated, the user just need to have the `sync` additional action assigned for the `Data Store` object permission. The issue is that is is not documented, but it should work fine.
adam commented 2025-12-29 20:31:56 +01:00
Author
Owner
Copy Link

@hhopjh commented on GitHub (Aug 14, 2023):

Thanks for comment! Which object type is responsible for the sync permission?

Screenshot 2023-08-14 at 12 44 14
@hhopjh commented on GitHub (Aug 14, 2023): Thanks for comment! Which object type is responsible for the `sync` permission? <img width="829" alt="Screenshot 2023-08-14 at 12 44 14" src="https://github.com/netbox-community/netbox/assets/18419207/f16651da-8ee8-494d-a209-a1ddd7e6958b">
adam commented 2025-12-29 20:31:56 +01:00
Author
Owner
Copy Link

@hhopjh commented on GitHub (Aug 14, 2023):

Oh I see. It should be configured like this:

Screenshot 2023-08-14 at 13 01 53
@hhopjh commented on GitHub (Aug 14, 2023): Oh I see. It should be configured like this: <img width="950" alt="Screenshot 2023-08-14 at 13 01 53" src="https://github.com/netbox-community/netbox/assets/18419207/fd0bc99d-6a58-485e-b44f-d758a3eb7ec5">
adam commented 2025-12-29 20:31:56 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Nov 13, 2023):

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. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Nov 13, 2023): 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. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
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: documentation
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#8068
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?