-
Notifications
You must be signed in to change notification settings - Fork 891
Bug: "coder gitssh" not functional on 0.12.2 #4913
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
Comments
Doing a release now with the fix! This was resolved with #4884, but we forgot to do a release. |
v0.12.3 is coming out now! ~15mins |
@kylecarbs Awesome!!! Didn't expect a response over the weekend! Our devs will be quite happy Monday :-) |
@ssmiller25 no problem at all! It's been released and should work! Let me know if you have any problems. |
@kylecarbs No luck on 0.12.3 :-(
Anything else I should look at? This was a brand-new dev instance I spun up after the 0.12.3 upgrade (which went flawlessly( |
Uh oh!
There was an error while loading. Please reload this page.
Recently upgrade our coder instance to 0.12.2. Coder itself is hosted in Kubernetes, and we deploy AWS EC2 development enviornments. WIth the upgrade to 0.12.2, and newly created or updated environments can no longer pull/push into Github repositories. Error messages below
This seems to be directly from the GIT_SSH_COMMAND environment variable that ties in coder's backend to the GIT SSH authentication:
I ran
coder login <mycoderinstace>
successfully, but did not make a difference.Older environments that were created on the 0.9.1 server, and still have the 0.9.1 agent, continue to work. If any of those environments are updated to the latest agent, they stop working with the symptoms above.
Is there anything I need to look at? I did update the template to the latest Terraform provider.
The text was updated successfully, but these errors were encountered: