Add Nextcloud datasource

[bdovaz]

Tell us more.

In case anyone doesn't know what Nextcloud is: https://nextcloud.com/

Allows you to install apps found in: https://apps.nextcloud.com/

The list of apps and different versions is taken from this URL: https://apps.nextcloud.com/api/v1/platform/31.0.7/apps.json

I would like to create a PR to add this new data source, but I have never come across a data source that requires setting the version (https://apps.nextcloud.com/api/v1/platform/{version}/apps.json) through the renovate configuration.

Is there an example?

[rarkins]

I'm not aware of any either, but perhaps it can simply be provided in registryUrls. I assume that you must be able to get the platform version (e.g. 31.0.7) from the repo?

[bdovaz]

I'm not aware of any either, but perhaps it can simply be provided in registryUrls. I assume that you must be able to get the platform version (e.g. 31.0.7) from the repo?

@rarkins I currently have it as a custom data source:

"customDatasources": {
    "nextcloud": {
        "defaultRegistryUrlTemplate": "https://apps.nextcloud.com/api/v1/platform/31.0.7/apps.json",
        "transformTemplates": [
            "{\"releases\": $map($[id = '{{packageName}}'].releases, function($r) { { \"version\": $r.version, \"releaseTimestamp\": $r.created, \"isStable\": $not($r.isNightly) } })[] }"
        ]
    }
},

And so that I don't have to update that 31.0.7 manually, I have a renovate rule in the renovate configuration file itself:

"customManagers": [
    {
        "customType": "regex",
        "managerFilePatterns": ["/(^|/)renovate.json$/"],
        "matchStrings": [
            "https://apps.nextcloud.com/api/v1/platform/(?<currentValue>.*)/apps.json"
        ],
        "depNameTemplate": "nextcloud/server",
        "datasourceTemplate": "github-releases"
    }
]

That's why I'm asking what you think would be the best way to transfer this to a PR that adds this data source.

I see two problems:

• The data source cannot have a default registry URL, because having to put a version in the registry URL will make it outdated. In other words, it would have to be provided from the renovate configuration.
• The need to create the custom manager (second snippet) so that the registry version does not have to be maintained manually. I don't know if it could be used as an example in the readme.md of the data source itself.

[rarkins]

I'm suggesting:

• No changing our our datasource interface. platform version is part of registryUrl. This means no default registryUrl for the datasource
• Managers are responsible for populating registryUrls

Again, this is assuming that the platform version is found in the repo and can be extracted by a manager (e.g. custom manager) and put into registryUrls.

[bdovaz]

PR created and ready for review #37292