-
Notifications
You must be signed in to change notification settings - Fork 6
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
feat(app): switch git proxy to golang #993
Conversation
9d51b9b
to
d93c288
Compare
d93c288
to
23f6537
Compare
The integration tests are failing because the git-proxy shuts down before the autosave can be created when a session is stopped. This is exactly the problem that #951 will address. Therefore to keep the diffs sane I think that we should merge this PR first and then rebase #951 to work with this version of the git proxy. This occurs more rarely in practice (but it still does) because the old version of the git proxy does not handle the SIGTERM signal properly and waits until it receives SIGKILL from k8s 30 seconds later. This is enough in most cases to pass the integration tests. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
some total nitpicking, nothing major. feel free to ignore those
Co-authored-by: Viktor Gal <[email protected]>
Co-authored-by: Viktor Gal <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Found a bit better maintained proxy library in Go. This will resolve all the critical security vulnerabilities we have with the current node js proxy.
I also added tests for the proxy that ensure that the Git credentials are added in the right circumstances and edited the CI pipeline so that these tests run on every push.