Digest Support for Custom Datasources

[travisshivers]

Tell us more.

It would be great if custom datasources supported digests.

For example, if the datasource returned something like:

{
  "releases": [
    {
      "version": "main",
      "digest": "fe5edadd9524d5f3378ef39b7ba0b6224d7cf13e"
    }
  ]
}

[secustor]

This would make sense when the custom manager supports digest pinning or do you have a current use case too?

[travisshivers]

Yes, correct, I am aiming to use this with a custom manager for digest pinning too. The custom manager already seems to support digest pinning, so it's just the datasource that is missing digest support currently.

I've got it partially working in f9ee4d4 but without implement the full getDigest function because it seems that not enough of the config is passed to the function to properly get the defaultRegistryUrlTemplate unlike getReleases.

I am trying to get renovate to work with a build system that expresses repository dependencies similarly to git submodules.

And then with that, it works if I capture and pass along the digest as newDigest

  customManagers: [
    {
      customType: "regex",
      fileMatch: ["^myDeps.json$"],
      matchStringsStrategy: "recursive",
      matchStrings: [
        '"(?<depName>[^"]*)":\\s*{\\s*"commit":\\s*"(?<currentDigest>[^"]*)"',
      ],
      datasourceTemplate: "custom.myDatasourceWithDigest",
      "currentValueTemplate": "0000000000000000000000000000000000000000",
      "versioningTemplate": "git",
    },
  ],

  customDatasources: {
    myDatasourceWithDigest: {
      format: "json",
      defaultRegistryUrlTemplate: "http://my.api/{{ packageName }}",
      transformTemplates: [
        '{ "releases": $map(releases, function($v) { { "version": "0000000000000000000000000000000000000000", "newDigest": $v.digest } })[] }',
      ],
    },
  },

[secustor]

I have created a feature request #25197

[faenschi]

Thank you so much @secustor !