Fixes #718: Add token when getting NetBox version to prevent 403 error #724
+3
−3
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…prevent 403 error
jeremystretch
requested review from
a team and
bctiemann
and removed request for
a team
Contributor
Author
|
I sense v2 token-compatible pynetbox coming out soon, so I hope this PR could get reviewed before considering releasing new version. Thanks! |
bctiemann
approved these changes
Jan 8, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes: #718
Request.get_version()now includes the authorization token (if present in the API object) when calling NetBox/api/, to get the NetBox API version without causing 403 error in the NetBox reverse proxy and Django logs.