feat: add support for coder_git_auth data source
#6334
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mtojek
reviewed
Feb 27, 2023
mtojek
approved these changes
Feb 27, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This allows template authors to force Git authentication on workspace creation. It does not provide guarantees of Git authentication on subsequent builds at the moment, but that might change before merge.
TODO:
Add validation for Git authentication in the workspace build APIUpdate: I'll be adding support for forcing Git authentication during workspace builds once the startup script work @code-asher is working on is merged. Otherwise, it becomes a bit awkward.
I wasn't able to find a fantastic way to decompose this PR into smaller chunks. This only affects users that add the
coder_git_authblock to their templates!