Erez Rokah

Thought of another option. If the resource is a relation we can make it a column of the parent, similar to https://github.com/cloudquery/cloudquery/pull/12408#discussion_r1267911498

OK so we haven't seen many of these cases so I'm not sure we need a generic approach (or can have since we would need to verify the fields we...

We should also update https://www.cloudquery.io/docs/advanced-topics/migrations to reflect the new behavior

Going to close this for now. We haven't seen users requests to support the remaining destinations on this list. We can re-visit if needed

Initial implementation released in CLI version `v5.16.0`, see docs in https://docs.cloudquery.io/docs/reference/destination-spec#sync_group_id-preview

Closing this issue in favor of https://github.com/cloudquery/cloudquery/issues/8690. While not completely identical solutions, I think the use case is the same, so we can discuss on a the same issue

Initial work at https://github.com/cloudquery/plugin-sdk/pull/732

I think https://github.com/cloudquery/plugin-sdk/pull/732 resolved this

Note to readers, this requires a separate plugin from the GCP since the configuration is very different though the API library is the same one https://github.com/googleapis/google-cloud-go

Hi @bbernays, thank you for the PR 🚀 Can you explain a bit more what's missing from it?