Latest version number retrieval for CloudQuery open-core plugins issues

CloudQuery Plugins
1

Figure the answer is no, but as the saying goes, a closed mouth doesn’t get fed :sweat_smile:

With the open-core plugins (e.g., AWS and GCP are the ones I’m using), the only way to get the latest version number is from the new hub? Are the latest version numbers (even if the code isn’t) not going to be published to GitHub again? This breaks all our automation (Renovate) we use to keep our configs up to date, and I’d strongly prefer to not have to build a custom HTML parser in regex to keep all this updated.

2

Hi @sure-hound :wave:

You’re right, the only way to get the latest versions is from the Hub. We also have a bunch of automation around GitHub releases and Renovate to update configurations we use internally, for docs, etc. We’re planning to solve it via Renovate Custom Datasource Documentation.

curl https://api.cloudquery.io/plugins

returns a latest_version for each plugin, so the plan is to use that. Once we get it working, we can publish a guide for it. No GitHub releases break Renovate automation.

curl https://api.cloudquery.io/plugins/cloudquery/source/aws/versions

gives all versions.

Hi @sure-hound, it’s not a guide, but you can look at this GitHub comparison. It’s not a big change, mostly changing the datasource for the regex matchers to a custom one and extracting the data.

I’m still trying to get the changelogUrl bit to work, but I can confirm this is working for us, see this pull request.

3

Thank you for this - I’ll give this a shot first thing next week :tada: