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

Separate Address Fields for Site #8715

New Issue
Closed
opened 2025-12-29 20:40:16 +01:00 by adam · 4 comments
adam commented 2025-12-29 20:40:16 +01:00
Owner
Copy Link

Originally created by @i3D-RyanHamel on GitHub (Oct 4, 2023).

NetBox version

3.3.10

Feature type

Data model extension

Proposed functionality

Add separate fields for country, country + province/state, city, and postal/zip code.

Use case

For issue #9617, how about using RFC8805 as the reason to have specific fields for the country, country + province/state, city, and postal/zip code. Geofeeds are important when it comes to having geo IP database vendors like MaxMind poll in data changes on a periodic basis.

Database changes

No response

External dependencies

No response

Originally created by @i3D-RyanHamel on GitHub (Oct 4, 2023). ### NetBox version 3.3.10 ### Feature type Data model extension ### Proposed functionality Add separate fields for country, country + province/state, city, and postal/zip code. ### Use case For issue #9617, how about using [RFC8805](https://datatracker.ietf.org/doc/html/rfc8805) as the reason to have specific fields for the country, country + province/state, city, and postal/zip code. Geofeeds are important when it comes to having geo IP database vendors like MaxMind poll in data changes on a periodic basis. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurepending closure labels 2025-12-29 20:40:16 +01:00
adam closed this issue 2025-12-29 20:40:17 +01:00
adam commented 2025-12-29 20:40:17 +01:00
Author
Owner
Copy Link

@jsenecal commented on GitHub (Oct 18, 2023):

I am totally in support for this improvement. I had to rely on using google places ID in a customfield to be able to reliably store address information in a reliable form.

An alternative would be to write address in yaml ? But then end users could mess up the format and we end up with parsing errors... Unless using custom validators?... Down goes the rabbit hole 😄

@jsenecal commented on GitHub (Oct 18, 2023): I am totally in support for this improvement. I had to rely on using google places ID in a customfield to be able to reliably store address information in a reliable form. An alternative would be to write address in yaml ? But then end users could mess up the format and we end up with parsing errors... Unless using custom validators?... Down goes the rabbit hole 😄
adam commented 2025-12-29 20:40:18 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jan 17, 2024):

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 (Jan 17, 2024): 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).
adam commented 2025-12-29 20:40:18 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Feb 16, 2024):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Feb 16, 2024): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
adam commented 2025-12-29 20:40:18 +01:00
Author
Owner
Copy Link

@Cormoran96 commented on GitHub (Mar 25, 2024):

Someone has create an alternative to do this:

https://github.com/FrumentumNL/GeoBox

@Cormoran96 commented on GitHub (Mar 25, 2024): Someone has create an alternative to do this: https://github.com/FrumentumNL/GeoBox
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 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#8715
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?