feat: Add documentation and plugin publishing commands #8
Conversation
|
CC @mbillewicz @r--w |
|
@maaarcelino |
|
@mbillewicz Done. We'll take care of the initial publish. I've created a team for you on our Hub. Can you give me an email address for you/someone on your side so I can transfer the ownership? You can share it here or email me at marcel@cloudquery.io. |
|
@maaarcelino pls use it@coinpaprika.com |
|
@mbillewicz I've sent you an invite. Can you merge this PR, please? |
|
@maaarcelino nothing in inbox, could you send once again? |
|
@mbillewicz I just resent it. |
|
@maaarcelino what is the title of the email? I can't find it in my inbox, checked both main and spam folders for it@coinpaprika.com email. |
|
@r--w Apologies, I just found out that we haven't implemented the email feature for user invites. Can you register for an account using it@coinpaprika.com here https://cloud.cloudquery.io/auth/register? Once you have an account you'll see the invite in the UI. |
|
@maaarcelino I've created account, but can't see coinpaprika project and seems that name is already taken ;) |
As a follow up to #7 this PR adds code to publish this plugin to the Cloudquery Hub.
One of the new requirements is that plugin documentation live in the
docs/overview.mdfile. I've moved a chunk of the README into this new file. I also modified the documentation generation to use thecloudquery tablesCLI command and added an option for controlling the concurrency of a sync.