Error configuring GitLab CI_REGISTRY setting using registryAliases

[dandn]

How are you running Renovate?

Self-hosted

If you're self-hosting Renovate, tell us what version of Renovate you run.

whitesource/renovate-on-prem v2.5.1 (renovate 32.185.3)

If you're self-hosting Renovate, select which platform you are using.

GitLab self-hosted

If you're self-hosting Renovate, tell us what version of the platform you run.

GitLab EE

Was this something which used to work for you, and then stopped?

I never saw this working

Describe the bug

As initially discussed here.

I'm having an issue configuring CI_REGISTRY following the documentation here.

For a given GitLab repo I attempted to add a registryAliases entry by updating the renovate.json file as follows:

{
  "$schema": "https://docs.renovatebot.com/renovate-schema.json",
  "dependencyDashboard": true,
  "registryAliases": {
    "$CI_REGISTRY": "docker-registry.mycompany.net"
  }
}

This approach does not work as I get the following Action Required: Fix Renovate Configuration generated under GitLab issues:

Location: renovate.json
Error type: The renovate configuration file contains some invalid settings
Message: Invalid 'registryAliases.registryAliases.$CI_REGISTRY' configuration: value is not a url

As mentioned in the initial discussion, it's expecting the URL to be in format https://...... That validation might be too strict. E.g. in my example above, using https://docker-registry.mycompany.net will not generate the renovate error.
However, prepending the https results in incorrectly formatted docker images.

Perhaps there is an expectation that this setting belongs exclusively in config.js? In this case, a documentation fix seems in order.

Maybe the code needs to be modified to properly handle a CI_REGISTRY assignment?

Relevant debug logs

Logs

Have you created a minimal reproduction repository?

No reproduction repository

[bitnik]

We had the same problem today. Adding registryAliases into config.js solves the issue and renovate runs through. But renovate-config-validator still fails with the same error ("value is not a url") even it is configured in config.js.

[rarkins]

Workaround is to put them in config.js as noted by @bitnik. I guess we may need to loosen our validation for registryAliases as the longer term solution.

[github-actions]

Hi there,

Get your issue 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.

To get started, please read our guide on creating a minimal reproduction.

We may close the issue if you, or someone else, haven't created a minimal reproduction within two weeks. If you need more time, or are stuck, please ask for help or more time in a comment.

Good luck,

The Renovate team

[github-actions]

When a bug has been marked as needing a reproduction, it means nobody can work on it until one is provided. In cases where no reproduction is possible, or the issue creator does not have the time to reproduce, we unfortunately need to close such issues as they are non-actionable and serve no benefit by remaining open. This issue will be closed after 7 days of inactivity.

[PatrickSpies]

Minimal reproduction: https://github.com/PatrickSpies/renovate-17963

[rarkins]

Reproduction forked to https://github.com/renovate-reproductions/17963

[renovate-release]

🎉 This issue has been resolved in version 35.122.0 🎉

The release is available on:

• GitHub release
• 35.122.0

Your semantic-release bot 📦🚀