Fix: Add useHttpPath to support multiple Git credentials on same host #9143
+86
−1
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.
Changes
This PR fixes a bug where multiple Git repositories on the same host could not use different credentials. When users linked multiple secrets to a ServiceAccount for different repositories on the same Git server (e.g.,
github.com/org/repo1andgithub.com/org/repo2), Tekton would incorrectly use the first credential for all repositories, authentication failures. The root cause was that Git's credential helper only matched by hostname, ignoring the repository path. This fix addsuseHttpPath = trueto Git credential contexts, instructing Git to match credentials based on the full repository URL. The solution is backwards compatible, requires no configuration changes, and includes comprehensive test coverage including a new test specifically for this scenario.TestBasicFlagHandlingMultipleReposSameHost to verify the fix
Submitter Checklist
As the author of this PR, please check off the items in this checklist:
/kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tepRelease Notes