Allow prefixes to be assigned to VLAN in other/no site

[heiko-ma]

NetBox version

v3.2.9

Feature type

Change to existing functionality

Proposed functionality

As described in #10104, it is currently not possible to assign a prefix to a VLAN in a VLAN group that isn't in the same site/site group. For some usecases (described below) it would be practical, if the prefix could be assigned to a VLAN which is either:

• in no site (i believe this is currently possible with VLANs -> they can be assigned to devices if they have no site)

• in a site which is higher up in the hierarchy of site groups/region, for example
  region "global" -> VLAN group is scoped to region and set to global
  region "south"
  site "A" -> Prefix is assigned to site which is child of the region

  ---

  site group "global" -> VLAN group is scoped to site group and set to global
  site group "campus A"
  site "A" -> Prefix is assigned to site which is child of the site group

Site groups or regions provide some kind of constraint in which objects can be assigned. If VLAN/VLAN group and prefix are in the same hierarchy, I see no issue in this.

Use case

In our company, every site has a basic set of VLANs that need to be implemented. To skip the need of creating this set for every new site, it would be beneficial if a "global scoped" set could be used and the prefixes would be assigned to this set. This would eliminate the need of creating the same VLAN all over again.

Database changes

No response

External dependencies

No response

[github-actions]

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]

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.