I see GitHub registry support has been deprecated. Is the intent to disallow community plugins?
Hey 
, this is not the intent. The intent was to support the CQ registry (where we can also provide docs and other experience for the users). Other than the CQ registry, we mostly wanted to support generic remotes like Docker, local file, and not GitHub. Because after GitHub, there is GitLab, Gitea, and so on, and it doesn’t really scale.
So essentially, you can always host it anywhere and just download the plugin and run it with a local registry, but the hub should provide the best experience and work for community plugins. I’m happy to hear if we missed a use case, though?
Maybe an HTTP registry would be helpful. That way we could target releases hosted by GitHub, GitLab, Gitea, and so on.
Yea, that would be a great solution. Cool, I will open an issue!
Github registry was a pretty good user experience. Without it, we need our own tool to fetch Github release binaries and then inject the local path into the .spec. It’s not impossible, but it’s a regression.
Why not use our hub though? You will get docs versioning as well?
I guess I’m not up to speed on the instructions to publish to the hub.
We originally had to start maintaining our own plugin forks because you told us to: cloudquery/plugin-sdk/pull/1141#issuecomment-1674307558
This is the recommended way to publish plugins, and it will appear on hub.cloudquery.io (you can make it private as well). For more information, check out the documentation: Publishing a Plugin to the Hub.