fix: enhance git remote validation by trying SSH URLs for generic hosts

[zzoubian]

Description

Fixes apm install fails the pre-install validation step when targeting a self-hosted Git server

Fixes #583

Type of change

• Bug fix
• New feature
• Documentation
• Maintenance / refactor

Testing

• Tested locally
• All existing tests pass
• Added tests for new functionality (if applicable)

[zzoubian]

@zzoubian please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.

@microsoft-github-policy-service agree [company="{your company}"]

Options:

• (default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.

@microsoft-github-policy-service agree

• (when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.

@microsoft-github-policy-service agree company="Microsoft"

Contributor License Agreement

Contribution License Agreement

This Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”), and conveys certain license rights to Microsoft Corporation and its affiliates (“Microsoft”) for Your contributions to Microsoft open source projects. This Agreement is effective as of the latest signature date below.

1. Definitions.
   “Code” means the computer software code, whether in human-readable or machine-executable form,
   that is delivered by You to Microsoft under this Agreement.
   “Project” means any of the projects owned or managed by Microsoft and offered under a license
   approved by the Open Source Initiative (www.opensource.org).
   “Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to any
   Project, including but not limited to communication on electronic mailing lists, source code control
   systems, and issue tracking systems that are managed by, or on behalf of, the Project for the purpose of
   discussing and improving that Project, but excluding communication that is conspicuously marked or
   otherwise designated in writing by You as “Not a Submission.”
   “Submission” means the Code and any other copyrightable material Submitted by You, including any
   associated comments and documentation.
2. Your Submission. You must agree to the terms of this Agreement before making a Submission to any
   Project. This Agreement covers any and all Submissions that You, now or in the future (except as
   described in Section 4 below), Submit to any Project.
3. Originality of Work. You represent that each of Your Submissions is entirely Your original work.
   Should You wish to Submit materials that are not Your original work, You may Submit them separately
   to the Project if You (a) retain all copyright and license information that was in the materials as You
   received them, (b) in the description accompanying Your Submission, include the phrase “Submission
   containing materials of a third party:” followed by the names of the third party and any licenses or other
   restrictions of which You are aware, and (c) follow any other instructions in the Project’s written
   guidelines concerning Submissions.
4. Your Employer. References to “employer” in this Agreement include Your employer or anyone else
   for whom You are acting in making Your Submission, e.g. as a contractor, vendor, or agent. If Your
   Submission is made in the course of Your work for an employer or Your employer has intellectual
   property rights in Your Submission by contract or applicable law, You must secure permission from Your
   employer to make the Submission before signing this Agreement. In that case, the term “You” in this
   Agreement will refer to You and the employer collectively. If You change employers in the future and
   desire to Submit additional Submissions for the new employer, then You agree to sign a new Agreement
   and secure permission from the new employer before Submitting those Submissions.
5. Licenses.

• Copyright License. You grant Microsoft, and those who receive the Submission directly or
  indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license in the
  Submission to reproduce, prepare derivative works of, publicly display, publicly perform, and distribute
  the Submission and such derivative works, and to sublicense any or all of the foregoing rights to third
  parties.
• Patent License. You grant Microsoft, and those who receive the Submission directly or
  indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license under
  Your patent claims that are necessarily infringed by the Submission or the combination of the
  Submission with the Project to which it was Submitted to make, have made, use, offer to sell, sell and
  import or otherwise dispose of the Submission alone or with the Project.
• Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement.
  No additional licenses or rights whatsoever (including, without limitation, any implied licenses) are
  granted by implication, exhaustion, estoppel or otherwise.

6. Representations and Warranties. You represent that You are legally entitled to grant the above
   licenses. You represent that each of Your Submissions is entirely Your original work (except as You may
   have disclosed under Section 3). You represent that You have secured permission from Your employer to
   make the Submission in cases where Your Submission is made in the course of Your work for Your
   employer or Your employer has intellectual property rights in Your Submission by contract or applicable
   law. If You are signing this Agreement on behalf of Your employer, You represent and warrant that You
   have the necessary authority to bind the listed employer to the obligations contained in this Agreement.
   You are not expected to provide support for Your Submission, unless You choose to do so. UNLESS
   REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING, AND EXCEPT FOR THE WARRANTIES
   EXPRESSLY STATED IN SECTIONS 3, 4, AND 6, THE SUBMISSION PROVIDED UNDER THIS AGREEMENT IS
   PROVIDED WITHOUT WARRANTY OF ANY KIND, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY OF
   NONINFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.
7. Notice to Microsoft. You agree to notify Microsoft in writing of any facts or circumstances of which
   You later become aware that would make Your representations in this Agreement inaccurate in any
   respect.
8. Information about Submissions. You agree that contributions to Projects and information about
   contributions may be maintained indefinitely and disclosed publicly, including Your name and other
   information that You submit with Your Submission.
9. Governing Law/Jurisdiction. This Agreement is governed by the laws of the State of Washington, and
   the parties consent to exclusive jurisdiction and venue in the federal courts sitting in King County,
   Washington, unless no federal subject matter jurisdiction exists, in which case the parties consent to
   exclusive jurisdiction and venue in the Superior Court of King County, Washington. The parties waive all
   defenses of lack of personal jurisdiction and forum non-conveniens.
10. Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and
    supersedes any and all prior agreements, understandings or communications, written or oral, between
    the parties relating to the subject matter hereof. This Agreement may be assigned by Microsoft.

@microsoft-github-policy-service agree

[danielmeppiel]

Review Feedback

Thanks @zzoubian for tackling this! The SSH-first approach for generic hosts is sound. A few things need addressing before merge:

1. CLA not signed (blocker)

Please reply to the CLA bot comment with @microsoft-github-policy-service agree to sign the Contributor License Agreement.

2. Missing encoding="utf-8" on subprocess call (regression)

PR #591 (just merged) added encoding="utf-8" to all subprocess.run(..., text=True) calls to fix crashes on Windows with non-UTF-8 consoles (CP950/CP936). Your new subprocess.run call at line ~448 needs the same:

result = subprocess.run(
    cmd,
    capture_output=True,
    text=True,
    encoding="utf-8",  # <-- add this
    timeout=30,
    env=validate_env,
)

3. No unit tests

Please add tests covering:

• SSH URL tried first for generic hosts, succeeds
• HTTPS fallback when SSH fails
• Non-generic hosts (GitHub/GHES) skip SSH attempt

Note on _build_repo_url

The call to ado_downloader._build_repo_url(use_ssh=True) uses a private method. This is pre-existing (main already calls it for HTTPS), but worth noting for a future refactor to expose a public API for URL building.

Relationship with PR #587

This PR complements #587 (which fixes the download path for Gitea). They don't conflict -- #584 fixes validation, #587 fixes download. Both can merge independently.

[zzoubian]

Ok added unit tests and replied to CLA with
@microsoft-github-policy-service agree

[sergio-sisternes-epam]

Clean fix that aligns validation with the existing download behavior in _clone_with_fallback(). SSH-first for generic hosts, HTTPS fallback — well tested with 5 cases covering the happy path, fallback, and negative scenarios. All prior review feedback addressed.

CodeQL note: The CodeQL failure is a false positive on test URL strings — not a code issue.

[Copilot]

Pull request overview

Fixes pre-install validation failures for repositories on generic/self-hosted Git servers that are accessible via SSH but may require authentication over HTTPS, aligning validation behavior with the existing clone fallback strategy.

Changes:

• Update _validate_package_exists() to try git ls-remote over SSH first for generic (non-GitHub/non-ADO) hosts, then fall back to HTTPS.
• Add unit tests covering SSH-first probing, HTTPS fallback, and host-type-specific behavior (GitHub.com vs GHES).

Show a summary per file

File	Description
src/apm_cli/commands/install.py	Implements SSH-first git ls-remote probing for generic hosts with HTTPS fallback.
tests/unit/test_install_command.py	Adds unit tests to validate SSH-first probing behavior and ensure GitHub/GHES paths do not take the generic SSH-first route.

Copilot's findings

• Files reviewed: 2/2 changed files
• Comments generated: 2

[Copilot]

In the generic-host path, validate_env intentionally omits GIT_ASKPASS / GIT_CONFIG_GLOBAL (see above). Later in this function, the verbose stderr sanitization does stderr_snippet.replace(validate_env.get(env_var, ""), "***"); when the key is missing this replaces the empty string, producing garbled output. Guard the replacement so it only runs when the env var value is a non-empty string (or use token/url sanitizers instead of env var substitution).

[Copilot]

Docstring grammar: "A GHES host is treated as GitHub, not generic SSH probe is skipped." reads like a run-on sentence and is hard to parse. Reword to clearly state that GHES hosts are treated as GitHub and therefore skip the generic SSH-first probe.

Suggested change

	"""A GHES host is treated as GitHub, not generic SSH probe is skipped."""
	"""GHES hosts are treated as GitHub hosts and skip the generic SSH-first probe."""