Skip to content
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

Fix Git submodule update issue with SSH creds #792

Merged
merged 1 commit into from
May 30, 2021
Merged

Fix Git submodule update issue with SSH creds #792

merged 1 commit into from
May 30, 2021

Conversation

HeavyWombat
Copy link
Contributor

Changes

The credential look-up routine only set up the Git command line flags for the
Git clone command, but not for the subsequent submodule command. When a
user tried to use a repository with a submodule that required authentication as
well, the Git step failed.

Change code to store the respective credential command line arguments into a
separate slice so that it can be used for different Git commands.

Submitter Checklist

  • Includes tests if functionality changed/was added
  • Includes docs if changes are user-facing
  • Set a kind label on this PR
  • Release notes block has been filled in, or marked NONE

See the contributor guide
for details on coding conventions, github and prow interactions, and the code review process.

Release Notes

Fixed issue with the source step failing for Git repositories that contain submodules that require authentication.

The credential look-up routine only set up the Git command line flags for the
Git `clone` command, but not for the subsequent `submodule` command. When a
user tried to use a repository with a submodule that required authentication as
well, the Git step failed.

Change code to store the respective credential command line arguments into a
separate slice so that it can be used for different Git commands.
@HeavyWombat HeavyWombat added the kind/bug Categorizes issue or PR as related to a bug. label May 29, 2021
@openshift-ci openshift-ci bot added the release-note Label for when a PR has specified a release note label May 29, 2021
@openshift-ci openshift-ci bot requested review from otaviof and qu1queee May 29, 2021 22:07
Copy link
Member

@SaschaSchwarze0 SaschaSchwarze0 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
/approve

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label May 30, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 30, 2021

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: SaschaSchwarze0

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 30, 2021
@openshift-merge-robot openshift-merge-robot merged commit 7985e2d into shipwright-io:main May 30, 2021
@HeavyWombat HeavyWombat deleted the fix/git-submodule-ssh branch May 31, 2021 07:25
@adambkaplan adambkaplan added this to the release-v0.5.0 milestone Jun 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. kind/bug Categorizes issue or PR as related to a bug. lgtm Indicates that a PR is ready to be merged. release-note Label for when a PR has specified a release note
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants