-
Notifications
You must be signed in to change notification settings - Fork 33
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.
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
Include the pynautobot version in the User-Agent header by default #205
Comments
This looks like a duplicate of #199. It was noted in that issue that this is already possible by setting the header after instantiation, but I can understand the desire to not need an extra step.
Yes, that seems like an acceptable low-risk change to me if you're willing to do the leg work. |
Also, in our case, we have a large (and unknown. and ever-changing.) number of folks who are writing pynautobot-enabled scripts to access our data, and asking everyone to update their code to send the pynautobot version in the useragent is... impractical. =) |
I see the failure in the PR #206 ; is that a 'me' problem or a 'pipeline' problem? The test harness passes locally for me, modulo a |
I dug into this and, with a help from Slack, was ultimately able to trace this to an issue where |
Both PRs have been merged; AFAIC this can be closed, with my thanks. |
Thanks! |
We ran into a case recently where it would have been useful to have pynautobot send its version in a user-agent header (or similar) by default; something like:
python-pynautobot/1.5.2
. For example, this would allow us to reach out to specific users and let them know they can/should upgrade to a more recent version. I'm thinking a patch like this:...which applies cleanly against both the
ltm-1.6
anddevelop
branches. Thoughts? I'm happy to fork and submit PRs for either or both branches if this works for you. If it does, would you accept it into the LTM branch or is this purely a 2.x thing? It's obviously not a bugfix, but as we're still on nautobot 1.6, I gotta ask. I could also extend the header to include the python-requests version as well if that would be useful.The text was updated successfully, but these errors were encountered: