UnsupportedProtocolError when accessing registry in Bazel

[philsegal]

What would you like help with?

I think I found a bug

How are you running Renovate?

Self-hosted

If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.

GitHub

Please tell us more about your question or problem

When running renovate against a client repo, we use a local file on our servers for our bazel registry:
e.g.

common --registry file:https:///srv/some/folder/my-bazel-registry

This throws an UnsupportedProtocolError.

It would be great if renovate supported the file protocol.

Minimal reproducible example... https://github.com/philsegal/bazel-21814

Logs (if relevant)

Logs

WARN: Host error (repository=****/******)
       "hostType": "bazel",
       "packageName": "platforms",
       "err": {
         "name": "UnsupportedProtocolError",
         "code": "ERR_UNSUPPORTED_PROTOCOL",
         "message": "Unsupported protocol \"file:\"",
         "stack": "UnsupportedProtocolError: Unsupported protocol \"file:\"\n    at normalizeArguments (/usr/local/renovate/node_modules/.pnpm/[email protected]/node_modules/got/dist/source/core/index.js:521:23)\n    at got (/usr/local/renovate/node_modules/.pnpm/[email protected]/node_modules/got/dist/source/create.js:112:39)\n    at gotTask (/usr/local/renovate/lib/util/http/index.ts:79:27)\n    at httpTask (/usr/local/renovate/lib/util/http/index.ts:212:16)\n    at wrapWithRetry (/usr/local/renovate/lib/util/http/retry-after.ts:34:20)\n    at Http.request (/usr/local/renovate/lib/util/http/index.ts:234:19)\n    at Http.requestJson (/usr/local/renovate/lib/util/http/index.ts:293:17)\n    at BazelDatasource.getReleases (/usr/local/renovate/lib/modules/datasource/bazel/index.ts:46:34)\n    at /usr/local/renovate/lib/util/cache/package/decorator.ts:122:18\n    at getRegistryReleases (/usr/local/renovate/lib/modules/datasource/index.ts:77:15)\n    at huntRegistries (/usr/local/renovate/lib/modules/datasource/index.ts:118:13)\n    at fetchReleases (/usr/local/renovate/lib/modules/datasource/index.ts:291:15)\n    at lookupUpdates (/usr/local/renovate/lib/workers/repository/process/lookup/index.ts:134:56)\n    at Function.wrap (/usr/local/renovate/lib/util/stats.ts:38:20)\n    at fetchDepUpdates (/usr/local/renovate/lib/workers/repository/process/fetch.ts:58:42)\n    at /usr/local/renovate/lib/workers/repository/process/fetch.ts:104:23\n    at /usr/local/renovate/node_modules/.pnpm/[email protected]/node_modules/p-map/index.js:57:22",
         "options": {
           "headers": {
             "user-agent": "RenovateBot/37.365.0 (https://github.com/renovatebot/renovate)",
             "accept": "application/json"
           },
           "url": "file:https:///srv/some/folder/my-bazel-registry/modules/platforms/metadata.json",
           "hostType": "bazel",
           "username": "",
           "password": "",
           "method": "GET",
           "http2": false
         }
       }

[github-actions[bot]]

Hi there,

Get your discussion fixed faster by creating a minimal reproduction. This means a repository dedicated to reproducing this issue with the minimal dependencies and config possible.

Before we start working on your issue we need to know exactly what's causing the current behavior. A minimal reproduction helps us with this. Discussions without reproductions are less likely to be converted to Issues.

Please follow these steps:

1. Read our guide on creating a minimal reproduction.
2. Go to our minimal reproduction template repository.
3. Select the Use this template button to create a new repository based on the template.
4. Work on the minimal reproduction in your own repository.
5. Fill out the information in your repository's README.md.
6. Add the link to your reproduction to the first post of your Discussion. If you are not the original author, you can post a new comment with the link.

Good luck,

The Renovate team

[philsegal]

Reproduction link added to the original post.

[philsegal]

Hi, not sure if this has been looked at or missed? Would be great to get some eyes on it, thanks :-)

[rarkins]

1. Unsupported capabilities/features are not bugs. We intentionally give less attention when people do this, not more.
2. The reproduction is not minimal. I saw ~20 files, skipped it

To move forward, resubmit this as an idea/feature request, and suggest how/what Renovate would need to do in order to support the file-based registry concept. You also need to consider the security aspects, e.g. are you ok with allowing users to access any files off the system which is running Renovate (including /etc/passwd, etc).

[github-actions[bot]]

Hi there,

A maintainer reviewed the information, and decided that this is not a bug. To avoid confusing others, we will close this Discussion. Please keep reading as there is good news too!

The good news is that the maintainer likes your idea, in general. Please create a new Suggest an Idea Discussion. Feel free to copy/paste what you need from this Discussion. Please focus on the feature request: explain what Renovate should do, and how Renovate can know when/what to do. We may convert that Discussion to an Issue when it is ready. Note that you will still have to wait for a maintainer, or someone else, to do the work needed for your feature.

Why are we closing your Discussion? For us, bug reports are about things that are not working as intended, or things that are not working as described in the docs. What you found may be bad behavior, but we do not think it is a bug.

For more details, please read our development docs about bug handling.

Thanks, the Renovate team