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.

Sign up for GitHub

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

Jump to bottom

Increase custom field integer ranges (from 32bit signed int to 64bit signed int) #14240

Closed
jwbensley opened this issue Nov 10, 2023 · 0 comments
Closed

Increase custom field integer ranges (from 32bit signed int to 64bit signed int) #14240

jwbensley opened this issue Nov 10, 2023 · 0 comments
Assignees
@jeremystretch
Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application
Milestone
v3.7

Comments

@jwbensley
Copy link

jwbensley commented Nov 10, 2023 •
edited
Loading

NetBox version

v3.5.9

Feature type

Change to existing functionality

Proposed functionality

Allow values in the range supported by a 32 u-int, when creating a custom fields which are of type "integer".

Currently, the maximum value I can put in an "integer" custom field is for a signed 32bit int.

Maybe the solution is to bump the field to a be a 64-bit signed int, if you want to support negative numbers too?

Example:

Bildschirmfoto vom 2023-11-10 10-07-35

Use case

I want to store a BGP ASN number, which is a 32bit u-int.
I want to store a BGP Local Pref, which is a 32bit u-int.

Database changes

I assume some sort of schema change is required but I don't know, sorry.

External dependencies

Sorry, I don't know of any.
@jwbensley jwbensley added the type: feature Introduction of new functionality to the application label Nov 10, 2023
@jwbensley jwbensley changed the title Increase custom field integer ranges (from 32bit signed int to 64bit signed) Increase custom field integer ranges (from 32bit signed int to 64bit signed int) Nov 10, 2023
@jeremystretch jeremystretch added the status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation label Dec 7, 2023
@jeremystretch jeremystretch added this to the v3.7 milestone Dec 27, 2023
@jeremystretch jeremystretch self-assigned this Dec 27, 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 labels Dec 27, 2023
jeremystretch added a commit that referenced this issue Dec 27, 2023
@jeremystretch
Closes #14240: Increase min/max validation values for custom fields
25e27ee
@jeremystretch jeremystretch mentioned this issue Dec 27, 2023
Merged
jeremystretch added a commit that referenced this issue Dec 27, 2023
@jeremystretch
Closes #14240: Increase min/max validation values for custom fields
4eadc8c
@jeremystretch jeremystretch mentioned this issue Dec 29, 2023
Merged
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 27, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@jeremystretch jeremystretch

Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application
Projects
None yet
Milestone
v3.7
Development

No branches or pull requests
2 participants
@jwbensley @jeremystretch