bug: When publishing plugin documentation; version is pointing to the wrong plugin about cloudquery HOT 4 CLOSED

Hi @dsmith111 and thank you for opening the issue. Looks like we're missing some docs around this.

We replace the VERSION_ placeholder just before publishing so the doc file we upload actually has the correct version embedded, see

I believe the RegEx here just needs to be updated to accept "-" dash characters as it already appears to accept "_" delimiters.

This RegEx is not used in https://hub.cloudquery.io/. It' deprecated and was used when we had only a single version (the latest one) of the plugins docs published under https://docs.cloudquery.io/docs

from cloudquery.

My suggestion is to update the docs manually/automatically before publish each version

from cloudquery.

Thanks for the info @erezrokah. Yeah, docs would add a bit more clarity. I saw the official plugins used a "VERSION" place-holder, and when I used that placeholder myself, with the tool name, it was automatically replaced after running cloudquery publish with the latest plugin version, so I assumed this was just an undocumented feature. Similar to using _configuration.md with the ":configuration" flag in a different document to insert it.

from cloudquery.

undocumented feature. Similar to using _configuration.md with the ":configuration" flag in a different document to insert it.

Yeah, we used these placeholders during the migration from the old Website where we had only a single version each plugin's docs. They allowed us to have both docs versions up during the transition, and we'll be phasing out the placeholders now that all plugins are in the Hub

from cloudquery.