We have an important update regarding our CloudQuery CLI. Starting today, a login will be required for all plugins and their versions released after this date. This affects plugin downloads from CloudQuery registry using the cloudquery sync, migrate, tables and the plugin install commands, and also using API.

If you're not already using a login to access CloudQuery, you'll need to start doing so. Further details on this are contained later in this update.

This change allows us to protect our CloudQuery hub backend, gather usage statistics, enabling us to tailor our product to your needs and helping us prioritize support and improvements to the plugins that need it the most. This means new integrations that meet our customers' needs and support for new features and other enhancements to our existing library of integrations.

There are two ways to authenticate with the CLI: using the cloudquery login command (see documentation), or using an API key in an environment variable.

We appreciate your understanding and look forward to the continued growth of CloudQuery together. As ever, we're keen to hear any feedback that you have about the integrations that you are already using or any new ones that would improve your experience. You can always share this feedback in the CloudQuery Community.

Data we are collecting when a plugin is downloaded:

Ready to get started with CloudQuery? You can try out CloudQuery locally with our quick start guide or explore the CloudQuery Platform (currently in beta) for a more scalable solution.

Want help getting started? Join the CloudQuery community to connect with other users and experts, or message our team directly here if you have any questions.