I think it could do the key gen as well with the right apis in place. Make call to request key, get key and update local .env. I checked with project management and this is not on our radar in the near future. What i suggest is for you to go to the CLI github issues page found here https://github.co...

I think it could do the key gen as well with the right apis in place.

That would be cool.  If i understand you correctly you are saying the cli can inspect the local application and request all the needed services, workspace, etc in the console for you and set it all up.  Is that right? If so I think that would be cool.  I don't think we are there yet but we could che...

I have asked around and we have no formal material built to help support multi org distribution.  It's on the list for a blog post in the future but I don't think that will help you in the short term.   Basically, our guidance at this time is to use CI/CD build pipelines to automate the manual proce...

The question of cross org distribution is a good question.  The bad news is there is not a super simple turn-key way to do this today.  The good news is we have a release in the works for this year that will bring cross org deployment up to that turn-key level.  Until that is released you will need ...

Is that TLS issue still persisting for you with node 14? 

In your projects root folder is a file named package.json.  in there you need to update the node support from ^10 || ^12 to 12^ || 14^.  I will send you a video on how to do it via messaging.  The video will be posted to YouTube Adobe Developer channel next week. Cheers

here is an article on some future expansion https://medium.com/adobetech/the-future-of-project-firefly-b2b-and-b2c-expansion-89de7ec60610

What expanded capabilities would you like to see added?

is xxxxxxx really your tenant id value? I am guessing here but that seems like a placeholder. https://xxxxxxx.campaign-sandbox.adobe.com/