-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Warn when using a client that doesn't match the server version #1040
Comments
@nickethier I'm looking to get involved with this project. I just tried running a |
Awesome @drewgonzales360! Do let us know if you have any questions. I or someone from the Nomad team will be happy to answer. |
👋 @nickethier, I could some early feedback on my PR. Can you take a 👀 and let me know if I'm heading the right direction? |
Is this still being worked upon? |
@danishprakash we've got a PR open #9159 which has iterated on this idea a bit by exposing the server version in the |
My bad @tgross, I just totally missed the linked PR, thanks for the clarification. |
#9159 has been merged and will ship in the next regular version of Nomad (likely Nomad 1.4.3). |
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues. |
A few times I've upgrade my server and nodes but forgot to update my local computer's version of nomad. It seems that older versions can still send commands but every once in a while I get pooched. For example, I was using 0.3.0 locally and 0.3.1 on the server, I was trying to test a job with artifacts. No errors came my way, turns out the 0.3.0 client was not passing along the artifact config.
Would it make sense to print a warning message when using a client that doesn't match the server version?
The text was updated successfully, but these errors were encountered: