Skip to content

Commit 55e9685

Browse files
jeremystretchjeremystretch
authored
Merge pull request #7317 from netbox-community/develop
Release v3.0.3
2 parents b55c85b + d2dcc51 commit 55e9685

File tree

99 files changed

+1290
-742
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

99 files changed

+1290
-742
lines changed

‎.gitattributes‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
*.sh text eol=lf
2-
# Treat minified or packed JS/CSS files as binary, as they're not meant to be human-readable
3-
*.min.* binary
4-
*.map binary
5-
*.pack.js binary
2+
# Treat compiled JS/CSS files as binary, as they're not meant to be human-readable
3+
netbox/project-static/dist/*.css binary
4+
netbox/project-static/dist/*.js binary
5+
netbox/project-static/dist/*.js.map binary

‎.github/ISSUE_TEMPLATE/bug_report.yaml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ body:
1717
What version of NetBox are you currently running? (If you don't have access to the most
1818
recent NetBox release, consider testing on our [demo instance](https://demo.netbox.dev/)
1919
before opening a bug report to see if your issue has already been addressed.)
20-
placeholder: v3.0.2
20+
placeholder: v3.0.3
2121
validations:
2222
required: true
2323
- type: dropdown

‎.github/ISSUE_TEMPLATE/feature_request.yaml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ body:
1414
attributes:
1515
label: NetBox version
1616
description: What version of NetBox are you currently running?
17-
placeholder: v3.0.2
17+
placeholder: v3.0.3
1818
validations:
1919
required: true
2020
- type: dropdown

‎docs/administration/permissions.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
NetBox v2.9 introduced a new object-based permissions framework, which replace's Django's built-in permissions model. Object-based permissions enable an administrator to grant users or groups the ability to perform an action on arbitrary subsets of objects in NetBox, rather than all objects of a certain type. For example, it is possible to grant a user permission to view only sites within a particular region, or to modify only VLANs with a numeric ID within a certain range.
44

5-
{!docs/models/users/objectpermission.md!}
5+
{!models/users/objectpermission.md!}
66

77
### Example Constraint Definitions
88

‎docs/administration/replicating-netbox.md‎

Lines changed: 0 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -71,14 +71,3 @@ To extract the saved archive into a new installation, run the following from the
7171
```no-highlight
7272
tar -xf netbox_media.tar.gz
7373
```
74-
75-
---
76-
77-
## Cache Invalidation
78-
79-
If you are migrating your instance of NetBox to a different machine, be sure to first invalidate the cache on the original instance by issuing the `invalidate all` management command (within the Python virtual environment):
80-
81-
```no-highlight
82-
# source /opt/netbox/venv/bin/activate
83-
(venv) # python3 manage.py invalidate all
84-
```

‎docs/configuration/optional-settings.md‎

Lines changed: 56 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -490,6 +490,14 @@ NetBox can be configured to support remote user authentication by inferring user
490490

491491
---
492492

493+
## REMOTE_AUTH_GROUP_SYNC_ENABLED
494+
495+
Default: `False`
496+
497+
NetBox can be configured to sync remote user groups by inferring user authentication from an HTTP header set by the HTTP reverse proxy (e.g. nginx or Apache). Set this to `True` to enable this functionality. (Local authentication will still take effect as a fallback.) (Requires `REMOTE_AUTH_ENABLED`.)
498+
499+
---
500+
493501
## REMOTE_AUTH_HEADER
494502

495503
Default: `'HTTP_REMOTE_USER'`
@@ -498,6 +506,54 @@ When remote user authentication is in use, this is the name of the HTTP header w
498506

499507
---
500508

509+
## REMOTE_AUTH_GROUP_HEADER
510+
511+
Default: `'HTTP_REMOTE_USER_GROUP'`
512+
513+
When remote user authentication is in use, this is the name of the HTTP header which informs NetBox of the currently authenticated user. For example, to use the request header `X-Remote-User-Groups` it needs to be set to `HTTP_X_REMOTE_USER_GROUPS`. (Requires `REMOTE_AUTH_ENABLED` and `REMOTE_AUTH_GROUP_SYNC_ENABLED` )
514+
515+
---
516+
517+
## REMOTE_AUTH_SUPERUSER_GROUPS
518+
519+
Default: `[]` (Empty list)
520+
521+
The list of groups that promote an remote User to Superuser on Login. If group isn't present on next Login, the Role gets revoked. (Requires `REMOTE_AUTH_ENABLED` and `REMOTE_AUTH_GROUP_SYNC_ENABLED` )
522+
523+
---
524+
525+
## REMOTE_AUTH_SUPERUSERS
526+
527+
Default: `[]` (Empty list)
528+
529+
The list of users that get promoted to Superuser on Login. If user isn't present in list on next Login, the Role gets revoked. (Requires `REMOTE_AUTH_ENABLED` and `REMOTE_AUTH_GROUP_SYNC_ENABLED` )
530+
531+
---
532+
533+
## REMOTE_AUTH_STAFF_GROUPS
534+
535+
Default: `[]` (Empty list)
536+
537+
The list of groups that promote an remote User to Staff on Login. If group isn't present on next Login, the Role gets revoked. (Requires `REMOTE_AUTH_ENABLED` and `REMOTE_AUTH_GROUP_SYNC_ENABLED` )
538+
539+
---
540+
541+
## REMOTE_AUTH_STAFF_USERS
542+
543+
Default: `[]` (Empty list)
544+
545+
The list of users that get promoted to Staff on Login. If user isn't present in list on next Login, the Role gets revoked. (Requires `REMOTE_AUTH_ENABLED` and `REMOTE_AUTH_GROUP_SYNC_ENABLED` )
546+
547+
---
548+
549+
## REMOTE_AUTH_GROUP_SEPARATOR
550+
551+
Default: `|` (Pipe)
552+
553+
The Seperator upon which `REMOTE_AUTH_GROUP_HEADER` gets split into individual Groups. This needs to be coordinated with your authentication Proxy. (Requires `REMOTE_AUTH_ENABLED` and `REMOTE_AUTH_GROUP_SYNC_ENABLED` )
554+
555+
---
556+
501557
## RELEASE_CHECK_URL
502558

503559
Default: None (disabled)

‎docs/core-functionality/circuits.md‎

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
# Circuits
22

3-
{!docs/models/circuits/provider.md!}
4-
{!docs/models/circuits/providernetwork.md!}
3+
{!models/circuits/provider.md!}
4+
{!models/circuits/providernetwork.md!}
55

66
---
77

8-
{!docs/models/circuits/circuit.md!}
9-
{!docs/models/circuits/circuittype.md!}
10-
{!docs/models/circuits/circuittermination.md!}
8+
{!models/circuits/circuit.md!}
9+
{!models/circuits/circuittype.md!}
10+
{!models/circuits/circuittermination.md!}

‎docs/core-functionality/device-types.md‎

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
# Device Types
22

3-
{!docs/models/dcim/devicetype.md!}
4-
{!docs/models/dcim/manufacturer.md!}
3+
{!models/dcim/devicetype.md!}
4+
{!models/dcim/manufacturer.md!}
55

66
---
77

@@ -30,11 +30,11 @@ Once component templates have been created, every new device that you create as
3030
!!! note
3131
Assignment of components from templates occurs only at the time of device creation. If you modify the templates of a device type, it will not affect devices which have already been created. However, you always have the option of adding, modifying, or deleting components on existing devices.
3232

33-
{!docs/models/dcim/consoleporttemplate.md!}
34-
{!docs/models/dcim/consoleserverporttemplate.md!}
35-
{!docs/models/dcim/powerporttemplate.md!}
36-
{!docs/models/dcim/poweroutlettemplate.md!}
37-
{!docs/models/dcim/interfacetemplate.md!}
38-
{!docs/models/dcim/frontporttemplate.md!}
39-
{!docs/models/dcim/rearporttemplate.md!}
40-
{!docs/models/dcim/devicebaytemplate.md!}
33+
{!models/dcim/consoleporttemplate.md!}
34+
{!models/dcim/consoleserverporttemplate.md!}
35+
{!models/dcim/powerporttemplate.md!}
36+
{!models/dcim/poweroutlettemplate.md!}
37+
{!models/dcim/interfacetemplate.md!}
38+
{!models/dcim/frontporttemplate.md!}
39+
{!models/dcim/rearporttemplate.md!}
40+
{!models/dcim/devicebaytemplate.md!}

‎docs/core-functionality/devices.md‎

Lines changed: 14 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -1,29 +1,29 @@
11
# Devices and Cabling
22

3-
{!docs/models/dcim/device.md!}
4-
{!docs/models/dcim/devicerole.md!}
5-
{!docs/models/dcim/platform.md!}
3+
{!models/dcim/device.md!}
4+
{!models/dcim/devicerole.md!}
5+
{!models/dcim/platform.md!}
66

77
---
88

99
## Device Components
1010

1111
Device components represent discrete objects within a device which are used to terminate cables, house child devices, or track resources.
1212

13-
{!docs/models/dcim/consoleport.md!}
14-
{!docs/models/dcim/consoleserverport.md!}
15-
{!docs/models/dcim/powerport.md!}
16-
{!docs/models/dcim/poweroutlet.md!}
17-
{!docs/models/dcim/interface.md!}
18-
{!docs/models/dcim/frontport.md!}
19-
{!docs/models/dcim/rearport.md!}
20-
{!docs/models/dcim/devicebay.md!}
21-
{!docs/models/dcim/inventoryitem.md!}
13+
{!models/dcim/consoleport.md!}
14+
{!models/dcim/consoleserverport.md!}
15+
{!models/dcim/powerport.md!}
16+
{!models/dcim/poweroutlet.md!}
17+
{!models/dcim/interface.md!}
18+
{!models/dcim/frontport.md!}
19+
{!models/dcim/rearport.md!}
20+
{!models/dcim/devicebay.md!}
21+
{!models/dcim/inventoryitem.md!}
2222

2323
---
2424

25-
{!docs/models/dcim/virtualchassis.md!}
25+
{!models/dcim/virtualchassis.md!}
2626

2727
---
2828

29-
{!docs/models/dcim/cable.md!}
29+
{!models/dcim/cable.md!}

‎docs/core-functionality/ipam.md‎

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,19 +1,19 @@
11
# IP Address Management
22

3-
{!docs/models/ipam/aggregate.md!}
4-
{!docs/models/ipam/rir.md!}
3+
{!models/ipam/aggregate.md!}
4+
{!models/ipam/rir.md!}
55

66
---
77

8-
{!docs/models/ipam/prefix.md!}
9-
{!docs/models/ipam/role.md!}
8+
{!models/ipam/prefix.md!}
9+
{!models/ipam/role.md!}
1010

1111
---
1212

13-
{!docs/models/ipam/iprange.md!}
14-
{!docs/models/ipam/ipaddress.md!}
13+
{!models/ipam/iprange.md!}
14+
{!models/ipam/ipaddress.md!}
1515

1616
---
1717

18-
{!docs/models/ipam/vrf.md!}
19-
{!docs/models/ipam/routetarget.md!}
18+
{!models/ipam/vrf.md!}
19+
{!models/ipam/routetarget.md!}

0 commit comments

Comments
 (0)