Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Admin Settings - Git OAuth management #791

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

Closed
tjcran opened this issue Mar 31, 2022 · 3 comments
Closed

Admin Settings - Git OAuth management #791

tjcran opened this issue Mar 31, 2022 · 3 comments
Assignees
Labels
site Area: frontend dashboard

Comments

@tjcran
Copy link

tjcran commented Mar 31, 2022

This issue is to represent the work needed to include a Git OAuth management for Admin users in the UI. There will be related work that allows Users to connect their own Git account as well as backend work for both.

@tjcran tjcran changed the title Admin Settings - Git OAuth set-up Admin Settings - Git OAuth management Mar 31, 2022
@tjcran tjcran mentioned this issue Mar 31, 2022
4 tasks
@tjcran
Copy link
Author

tjcran commented Mar 31, 2022

Adding a comment from @Emyrk from the top level epic into this one
"One thing about git oauth applications in the product. We currently use oauth apps, which link to a single user. The issue with this, is that if we want to use git as a source for anything not bound to a user (eg a terraform yaml).

In v1, templates are WAC templates. The jank we have to do is iterate through users until we find a user that has access to the git repo for the WAC template. If we use an Application instead, the application has it's own perms to repos and can access the files directly.

In v2, I think we'll have the same problem, but with terraform files."

@f0ssel
Copy link
Contributor

f0ssel commented Mar 31, 2022

From https://www.notion.so/coderhq/V2-Scoping-SSH-Linked-Accounts-Dotfiles-f4e6e2747aaa4225b4b95f215e315fdb (this is an internal document link) we discussed this not being needed for initial release and can be something we revisit later once we have more feedback from the community.

@tjcran once you have confirmed we are good to push this back we can close

@tjcran tjcran added the Post-MVP label Apr 1, 2022
@tjcran
Copy link
Author

tjcran commented Apr 1, 2022

@f0ssel bumping to post-mvp as a "nice to have" to consider later, rather than closing

@misskniss misskniss added this to the Post-MVP milestone Apr 26, 2022
@misskniss misskniss added the site Area: frontend dashboard label Jun 14, 2022
@misskniss misskniss removed this from the Post-MVP milestone Jun 22, 2022
@f0ssel f0ssel closed this as completed Jul 28, 2022
@f0ssel f0ssel closed this as not planned Won't fix, can't repro, duplicate, stale Jul 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
site Area: frontend dashboard
Projects
None yet
Development

No branches or pull requests

3 participants