Add suport for GraphQL Mutations (write feature) #11877

Closed
opened 2025-12-29 21:51:07 +01:00 by adam · 5 comments
Owner

Originally created by @AdilsonTorres on GitHub (Nov 26, 2025).

NetBox version

v4.4.7

Feature type

New functionality

Proposed functionality

Hi, I believe adding support for GraphQL Mutations to modify Netbox objects would be a valuable feature, especially since the API is currently read-only.

Use case

Being able to manipulate NetBox and plugin data using GraphQL instead of the REST API.

Database changes

No response

External dependencies

No response

Originally created by @AdilsonTorres on GitHub (Nov 26, 2025). ### NetBox version v4.4.7 ### Feature type New functionality ### Proposed functionality Hi, I believe adding support for GraphQL Mutations to modify Netbox objects would be a valuable feature, especially since the API is currently read-only. ### Use case Being able to manipulate NetBox and plugin data using GraphQL instead of the REST API. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurepending closurestatus: revisions needednetbox labels 2025-12-29 21:51:07 +01:00
adam closed this issue 2025-12-29 21:51:07 +01:00
Author
Owner

@jeremystretch commented on GitHub (Dec 4, 2025):

@AdilsonTorres we've intentionally avoided supporting write operations since the GraphQ API was introduced in NetBox v3.0 due to concerns around performance and security. While we could potentially revisit the idea for a future release, the initiative would need to start with a much more fleshed-out feature request detailing the proposed implementation. Would you like to spend a few hours expanding this FR accordingly?

@jeremystretch commented on GitHub (Dec 4, 2025): @AdilsonTorres we've intentionally avoided supporting write operations since the GraphQ API was introduced in NetBox v3.0 due to concerns around performance and security. While we could potentially revisit the idea for a future release, the initiative would need to start with a much more fleshed-out feature request detailing the proposed implementation. Would you like to spend a few hours expanding this FR accordingly?
Author
Owner

@AdilsonTorres commented on GitHub (Dec 5, 2025):

@jeremystretch Yes, I can do that. Could you provide references or reasons for these concerns related to performance and security? I will try to enhance my FR in more detail. I would also apprecisate it if you could give some advice on the recommended structure for expandind this FR.

@AdilsonTorres commented on GitHub (Dec 5, 2025): @jeremystretch Yes, I can do that. Could you provide references or reasons for these concerns related to performance and security? I will try to enhance my FR in more detail. I would also apprecisate it if you could give some advice on the recommended structure for expandind this FR.
Author
Owner

@jeremystretch commented on GitHub (Dec 5, 2025):

I'm afraid I don't have any time to dedicate to this initiative. You'll have to search prior issues and discussions to see what concerns were raised, and coordinate with other interested volunteers.

If you're not sure how to go about this, I suggest closing this FR and starting instead with a discussion to source and refine an implementation strategy.

@jeremystretch commented on GitHub (Dec 5, 2025): I'm afraid I don't have any time to dedicate to this initiative. You'll have to search prior issues and discussions to see what concerns were raised, and coordinate with other interested volunteers. If you're not sure how to go about this, I suggest closing this FR and starting instead with a [discussion](https://github.com/netbox-community/netbox/discussions/new?category=ideas) to source and refine an implementation strategy.
Author
Owner

@github-actions[bot] commented on GitHub (Dec 13, 2025):

This is a reminder that additional information is needed in order to further triage this issue. If the requested details are not provided, the issue will soon be closed automatically.

@github-actions[bot] commented on GitHub (Dec 13, 2025): This is a reminder that additional information is needed in order to further triage this issue. If the requested details are not provided, the issue will soon be closed automatically.
Author
Owner

@github-actions[bot] commented on GitHub (Dec 21, 2025):

This issue is being closed as no further information has been provided. If you would like to revisit this topic, please first modify your original post to include all the requested detail, and then ask that the issue be reopened.

@github-actions[bot] commented on GitHub (Dec 21, 2025): This issue is being closed as no further information has been provided. If you would like to revisit this topic, please first modify your original post to include all the requested detail, and then ask that the issue be reopened.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#11877