Is it possible to publish packs to private registries ? #22018

Putting a token for the registry in the config file should be the right approach, but I think the URLs have to be an exact match for it to get picked up. So you would need to use http://127.0.0.1:5000/v2/ instead of just http://127.0.0.1:5000/.

@mbg I tried both, and it's still not working, still doing a query to the token endpoint

Sorry, I just had a look over the implementation and it looks like the credentials can't actually be configured in the config files themselves. Try setting the CODEQL_REGISTRIES_AUTH environment variable to "http://127.0.0.1:5000/v2/=<token>". It accepts a comma-separated list of <registry_url>=<token> pairs.

Ok better now, but I still have some issues after, I leave it opened, I'll do more testing

Hey @mbg actually CODEQL_REGISTRIES_AUTH is not working only the --registries-auth-stdin option:

$ export CODEQL_REGISTRIES_AUTH=https://custom.local/v2/=TOKEN1

$ codeql pack download codeql/csharp-queries -v
Package specifications to check for download: codeql/csharp-queries
Recording pack reference codeql/csharp-queries at /home/user/.codeql/packages/codeql/csharp-queries/1.7.5.
Packaging> Requesting package versions of codeql/csharp-queries from https://ghcr.io/v2/codeql/csharp-queries/tags/list?n=100
...