Other ask (sort of related to ^)
With the new pricing change: how do bug fixes work in the free tier? I noticed that some data is missing in a GCP table, and it’s a potential bug fix. If I’m pinned as a free user to the pre-premium, do I get important bug fixes like this, or will it require upgrades to get CloudQuery to perform “as expected” with pinned versions?
Looking into this, will get back to you.
Following up on this as I have a call later with @yevgenyp and I’m curious ahead of time.
Hi,
We don’t support ports for old versions and suggest that everyone stays on the latest version if possible. If there is a specific issue that a customer can’t upgrade due to, we can provide a backport, but this is only for paid customers.
I’m happy to open a free trial for you so that you can use the latest version without any limits.
The trial is a small piece, but it’s more or less trying to get a baseline that works before we negotiate, to be honest.
The bug fix for this is the difference between “free and doesn’t work” and “have to pay because it’s the only way it will work” for our SOX compliance tasks, given that it’s not a feature but missing data.
So we don’t have free anymore unfortunately as this business model didn’t work for us. We have a free quota and trial for all of our plugins. The framework is open source; the plugins are closed source.
Right, that I understand. Just unfortunate timing for our PoC to get a baseline to answer some SOX questions.
Maybe we can discuss on the call, but isn’t upgrading to the latest version supposed to be an easy fix?
The bug fix I need isn’t out and it’s also gated behind the new non-free pricing, meaning the PoC just went from MVP for a few questions to having to get a quote, negotiate, and get approval from finance.
Ok, let’s discuss on the call shortly, and see if it’s something we can help with. I just want to understand better the state of the PoC, etc.
PoC is:
Phase 1 - Just opt in a few pieces of AWS/GCP + all of K8s sources to answer a few SOX-related questions.
Build out monitoring/alerting/SLA to make sure the data flows and allow RO access to engineers (BigQuery) to run some queries.
Success is that the handful of use cases have answers (one use case falls short here in that CQ, until the bug fix, didn’t pick up default GCP IAM roles).
Phase 2 is to not call it a PoC and allow people to opt in more AWS tables in the sources as use cases arise (where being a paid customer is not a big deal).
So Phase 1 just escalated to requiring to be a paid customer before sign-off that it’s what we need, hence the poor timing.
We can go over it on the call, but that’s essentially the context.
(I realize there’s a free tier; it just gets messy as it went from free PoC to having a trial period, etc., which falls under finance approval.)
Totally understand, I got the context now. I think we will find a solution - looking forward to chatting!
@pretty-wolf we are on the call here - Zoom Meeting
Can you verify I’m good to go on the trial?
If so, do I simply create an API token under my user and follow the docs for how to use that?
Yes, you are good to go on the trial, and exactly you can create the API key. The new GCP plugin should be out shortly with the bug fix.
Already is 
I’m setting up my access to start a shared Slack channel, I’ll move that to email once I get that started. It requires an NDA and all that nonsense lol 
Thanks! Hopefully I can get y’all some cash, because frankly there aren’t any good alternatives.
Haha, thank you! I appreciate it and I’m excited to see it work for your use case!
I’m not seeing anything outside of the docs for cloudquery login. Is there something related to using the API token as an env var?
Yeah, probably we need to add a helper to cli/stdout - CloudQuery API Key Documentation
Do I need to run login with that env var, or does it “just work” if provided? That’s not clear.
It just works, login is not needed.