-
Notifications
You must be signed in to change notification settings - Fork 49
Closed
Labels
bugSomething isn't workingSomething isn't working
Milestone
Description
Description:
When attempting to apm install a package from an Azure DevOps repo where the project name contains spaces, APM reports
the package as "not accessible or doesn't exist" even though the repo is accessible via git ls-remote.
Steps to reproduce:
- Have a valid APM package hosted in an Azure DevOps repo under a project with spaces in the name (e.g., My Project
Name) - Run any of these variations:
apm install dev.azure.com/myorg/My%20Project%20Name/myrepo
apm install dev.azure.com/myorg/My+Project+Name/myrepo
apm install dev.azure.com/myorg/My Project Name/myrepo
apm install dev.azure.com/myorg/My%20Project%20Name/_git/myrepo - All fail with: ✗ ... - not accessible or doesn't exist
Expected behavior:
APM should handle URL-encoded spaces (%20) in Azure DevOps project names and successfully validate/install the
package.
Workaround confirmed:
Pushing the same repo to a project without spaces in the name succeeds validation (✓ accessible), confirming the issue
is specifically with space handling in project names.
Environment:
- APM CLI version: 0.7.3 (pip installation)
- OS: Windows 11
- The repo is confirmed accessible via git ls-remote with the %20-encoded URL
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working