-
Notifications
You must be signed in to change notification settings - Fork 881
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
Comments
Adding a comment from @Emyrk from the top level epic into this one 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." |
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 |
@f0ssel bumping to post-mvp as a "nice to have" to consider later, rather than closing |
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.
The text was updated successfully, but these errors were encountered: