I think this looks good! but I think we have to be cautions with gen turning into a product of itself which generates configs for various use-cases and so on so really important to keep it simple as I would even go far that gen is even not mandatory on it's own as it's quite common in most cases for users to create configs from documentation rather from commands that auto generate configs.

💯 This is a feature on its own. I'm trying to prevent the back and forth between CLI commands and manually editing files.
Another approach would be to make config creation/editing DX better (i.e. expose schema, have auto completion in IDE), but I think at the moment this is the fastest thing we can do to improve onboarding.

Because for example how do we know the user wants to sync the source with all destinations? so either he will have to add a destination or to delete a destination (not sure which is better I think to explicitly add might be better and the more secure way)

Yes I think this feature might change when we have more destinations (for example we can let the user chose from a list)

Also waiting on cloudquery/plugin-sdk#120 to merge this

Because for example how do we know the user wants to sync the source with all destinations? so either he will have to add a destination or to delete a destination (not sure which is better I think to explicitly add might be better and the more secure way)

Yes I think this feature might change when we have more destinations (for example we can let the user chose from a list)

I wouldn't go into the rabbit hole of adding more features like choosing from a list but rather just output the config and make this feature end at this. Im even at the opinion that the gen command is a bit too much but given we already have it and people like it we can keep it but wouldn't work on adding more features and interactivity to that as it's not the main goal of CQ (other we branch to auto-generating config product)

Got it, I'll close the PR so we can think this through