Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The sync permission for Data Source is not documented #12623

Closed
kkthxbye-code opened this issue May 16, 2023 · 5 comments
Closed

The sync permission for Data Source is not documented #12623

kkthxbye-code opened this issue May 16, 2023 · 5 comments
Assignees
Labels
status: accepted This issue has been accepted for implementation type: documentation A change or addition to the documentation

Comments

@kkthxbye-code
Copy link
Contributor

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.

@kkthxbye-code kkthxbye-code added type: documentation A change or addition to the documentation status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation labels May 16, 2023
@hhopjh
Copy link

hhopjh commented 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.

@kkthxbye-code
Copy link
Contributor Author

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.

@hhopjh
Copy link

hhopjh commented Aug 14, 2023

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

Screenshot 2023-08-14 at 12 44 14

@hhopjh
Copy link

hhopjh commented Aug 14, 2023

Oh I see. It should be configured like this:

Screenshot 2023-08-14 at 13 01 53

Copy link
Contributor

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 github-actions bot added the pending closure Requires immediate attention to avoid being closed for inactivity label Nov 13, 2023
@jeremystretch jeremystretch self-assigned this Dec 5, 2023
@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation and removed status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation pending closure Requires immediate attention to avoid being closed for inactivity labels Dec 5, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 5, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: accepted This issue has been accepted for implementation type: documentation A change or addition to the documentation
Projects
None yet
Development

No branches or pull requests

3 participants