Hello

I think this is a feature request on how connectors work. I'm using PyPi.org connector as an example here but I guess this can apply to many if not all public registries.

What would be awesome to see is if the connector could evalute if a remote package is compliant or not with the feeds policies, and if not try, another package version (depending on what violates the policy). E.g. newly published packages are blocked for two days, instead of always trying the latest version it would be check the date on PyPi.org and get a package that is compliant.

I know we can target a specific version in pip install, but for a big dependency graph that is not so user friendly to manually install a package dependency each time we get a error.

@dean-houston, thanks for fixing that bug and detailed response to dependencies.

Hello ProGet users and devs!

We have a server running on Linux server using podman and nginx reverse proxy. We have two feeds where one has a connector to the other. We want one feed with approved packages, and a team specific feed where they promote a subset for their own development (strict license requirements etc).
We have this configured using the internal hostname for the ProGet container (connector traffic does not leave the container).

But I'm starting this topic to ask if its expected behavior that formatting of uncached remote packages is a litte off? See screenshots.

And if anyone have experience with promoting packages including their dependencies I am open to suggestions. (Right now I'm thinking a script that first pull the packages, and the loop to pull/promote the depedencies)

Examples where "approved-pypi" is all approved packages, and "promoted-pypi" is our team specific feed with a subset of packages.
We have taken inspiration from the "Effective-Package-Management-in-Python" e-book.

Looking forward to your replies,
Gisle S.