Bug P2
Status Update
Comments
al...@doit.com <al...@doit.com> #2
Hi, could you please share screen shots of the UI you refer? Currently in the Cloud Source Repositories UI, in the top you will find:
YourRepository > Branch > file
You have a drop down in Repository and in Branch to change anytime.
Description
Hi team,
Problem Encountered:
Artifact Registry virtual repositories currently prioritize upstream repositories at the version level. When installing a package without specifying a version, pip defaults to the latest available version from any upstream repository, often bypassing the private repository if the specific version is missing. This behaviour limits the ability to fully prioritize private repositories and weakens protection against dependency confusion attacks.
What We Expected to Happen:
We expected an option for package-level fallback, where any package request—whether versioned or unversioned—first defaults to the private repository (higher-priority upstream). Only if the entire package is absent should the virtual repository consider lower-priority upstream repositories like PyPi.
Steps to Reproduce:
Observed Result:
pip defaults to the latest version available from PyPi, even when a version exists in the private repository. The priority configuration is applied only at the version level.
Workarounds Tried:
Feature Request:
Introduce an optional setting for package-level fallback in Artifact Registry virtual repositories. With this feature enabled:
Thank you!