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
Add GitLab OAuth flow the UI #1046
Conversation
48a89ee
to
81a9355
Compare
81a9355
to
dcf6c59
Compare
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.
Obviously this is 🔥 super hot fire 🔥. Nice!
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.
Nice and clean code structure. I only reviewed the Go code. LGTM
a02097a
to
643f707
Compare
da14f08
to
31b222a
Compare
31b222a
to
dc866c6
Compare
Added a new |
* Add ParseRepoURL API method * Add repo parsing to AddApp page * Add RepoInput component * Add Gitlab OAuth routes * Add gitlab OAuth UI elements * Prevent page content from overflowing * Add expiration fallback to jwt client * Add gitlab test for jwt client * Log middleware token verification errors * Store callback state before OAuth navigation * Remove unused variables from server suite test * Add CallbackState context * Use new Git-Provider-Token header name * Fix gitlab error message * Wrap RepoInput tests in callback context
Closes: #985
Adds Gitlab token retrieval to the UI:
https://drive.google.com/file/d/1w4zGgM_V1FCn4khD0Tp5DPzCO4kreEpa/view?usp=sharing
Also adds:
RepoInputWithAuth
component that seeks to encapsulate the auto-detection behavior.Known limitations:
Application
to GitLab via the UI; completing this work would conflict with the 768 new directory structure #1024 PR that is being worked onGit Provider
on the config repo. Specifying conflicting providers will result in an error.Git Provider
in a secret name stored on the cluster(!!!). Mixing and matching providers on the same cluster will result in errors. Again, this wasn't fixed as it would conflict with 768 new directory structure #1024.@JamWils Could you focus a review on the GitLab auth stuff
@joshri and @simon Could you check out the React stuff?