Frontend mode without explicit /<registry>/<namespace> in index URL

[shanduur]

At the moment PyOCI requires users to include /<registry>/<namespace> in the index URL. For example:

pip install --index-url="http://<user>:<pass>@<pyoci-url>/<registry>/<namespace>/" <package>

This works, but it is verbose and not always convenient. It also implicitly gives users access to any registry/namespace they specify in the URL, rather than limiting access to a predefined one.

Proposal

Introduce a "frontend mode" where PyOCI assumes the registry and namespace from an environment variable, for example:

PYOCI_REGISTRY_NAMESPACE="ghcr.io/allexveldman"

With this set, users could install packages with a shorter command:

pip install --index-url="http://<user>:<pass>@<pyoci-url>" <package>

[AllexVeldman]

In general the index-url is defined in a config file like pyproject.toml or pip.conf so everyone working on the project does not have to remember where to pull the package(s) from.
So the verbosity of the URL is not something I face often.

Hiding where the actual package comes from is not something I like..

I could imagine larger organisations to want to relocate internal packages without having to update hundreds of repos/branches, but that kind of organisation generally has better tools for the job, like artifactory.

It also implicitly gives users access to any registry/namespace they specify in the URL, rather than limiting access to a predefined one.

You can use any registry/namespace but access is controlled by the upstream OCI registry, PyOCI does not make assumptions about what you can and can't access.