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

Support for RESP3 #11540

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

Originally created by @jrtct on GitHub (Aug 29, 2025).

NetBox version

v4.3.7

Feature type

New functionality

Proposed functionality

Support for using RESP3 as a protocol when connecting to redis/valkey servers.

Use case

We are running Netbox in a kubernetes cluster using the helm chart. Because there aren't a lot of good options for running redis clusters in kubernetes we are using infinispan (with the infinispan operator), which is compatible with redis clients. Unfortunately, infinispan only supports RESP3, not RESP2 and netbox seems to use RESP2 by default. If there were an option for enabling RESP3 we could use it with our infinispan clusters natively.

It could theoretically also futureproof connections to redis/valkey servers if they ever drop support for RESP2.

Database changes

None

External dependencies

None

Originally created by @jrtct on GitHub (Aug 29, 2025). ### NetBox version v4.3.7 ### Feature type New functionality ### Proposed functionality Support for using RESP3 as a protocol when connecting to redis/valkey servers. ### Use case We are running Netbox in a kubernetes cluster using the [helm chart](https://github.com/netbox-community/netbox-chart). Because there aren't a lot of good options for running redis clusters in kubernetes we are using infinispan (with the infinispan operator), which is compatible with redis clients. Unfortunately, infinispan only supports RESP3, not RESP2 and netbox seems to use RESP2 by default. If there were an option for enabling RESP3 we could use it with our infinispan clusters natively. It could theoretically also futureproof connections to redis/valkey servers if they ever drop support for RESP2. ### Database changes None ### External dependencies None
adam added the type: featurepending closurestatus: revisions needed labels 2025-12-29 21:46:34 +01:00
adam closed this issue 2025-12-29 21:46:34 +01:00
adam commented 2025-12-29 21:46:34 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 29, 2025):

Thank you for your interest in extending NetBox. Unfortunately, the information you have provided does not constitute an actionable feature request. Per our contributing guide, a feature request must include a thorough description of the proposed functionality, including any database changes, new views or API endpoints, and so on. It must also include a detailed use case justifying its implementation. If you would like to elaborate on your proposal, please modify your post above. If sufficient detail is not added, this issue will be closed.

@jeremystretch commented on GitHub (Aug 29, 2025): Thank you for your interest in extending NetBox. Unfortunately, the information you have provided does not constitute an actionable feature request. Per our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md), a feature request must include a thorough description of the proposed functionality, including any database changes, new views or API endpoints, and so on. It must also include a detailed use case justifying its implementation. If you would like to elaborate on your proposal, please modify your post above. If sufficient detail is not added, this issue will be closed.
adam commented 2025-12-29 21:46:34 +01:00
Author
Owner
Copy Link

@jrtct commented on GitHub (Aug 29, 2025):

@jeremystretch thanks for your input, but I'm unsure what is meant by an "actionable feature request". I don't think that the request would include any changes to the database views or API endpoints, but it is simply a change in the configuration.

I'm unsure how netbox uses redis exactly, but it seems to be using Django and there it is a question of appending an option to the connection string.

I can add a bit more details to the use case, but I don't think it has many other benefits than supporting Infinispan (and possible futureproofing if redis/valkey ever drop support for RESP2).

Maybe the scope of a "feature request" is a bit too narrow for what I want. Feel free to let me know if it makes more sense to direct it somewhere else.

@jrtct commented on GitHub (Aug 29, 2025): @jeremystretch thanks for your input, but I'm unsure what is meant by an "actionable feature request". I don't think that the request would include any changes to the database views or API endpoints, but it is simply a change in the configuration. I'm unsure how netbox uses redis exactly, but it seems to be using Django and there it is a question of appending an option to the [connection string](https://django-valkey.readthedocs.io/en/latest/configure/advanced_configurations/#resp3-support). I can add a bit more details to the use case, but I don't think it has many other benefits than supporting Infinispan (and possible futureproofing if redis/valkey ever drop support for RESP2). Maybe the scope of a "feature request" is a bit too narrow for what I want. Feel free to let me know if it makes more sense to direct it somewhere else.
adam commented 2025-12-29 21:46:34 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Sep 6, 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 (Sep 6, 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.
adam commented 2025-12-29 21:46:35 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Sep 14, 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 (Sep 14, 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.
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 pending closure status: revisions needed 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#11540
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?