You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Python SDK should implement all the console endpoints as described in the Console API spec.
I noticed there is a project called an SDK generator (https://github.com/appwrite/sdk-generator). How close do you see it as being functional? I would be happy to work on updating this Python SDK, but in case the generator is being implemented in the next version, there is no need to work on this SDK manually.
🎤 Pitch
At the moment, we are looking for example:
Create account
Create account session (email)
Create project
Create team
Doing these via the API allows all the console activities to be performed automatically (such as provisioning a new instance). These API endpoints exists already and there is no reason they wouldn't be included in the SDK's.
👀 Have you spent some time to check if this issue has been raised before?
@markusleh, thanks for raising this issue! 🙏🏼 If we were to have it, the console API would be a separate package, and I'm not sure if it's something we want to maintain at the moment.
For the moment, you're free to make the API calls manually.
🔖 Feature description
Python SDK should implement all the console endpoints as described in the Console API spec.
I noticed there is a project called an SDK generator (https://github.com/appwrite/sdk-generator). How close do you see it as being functional? I would be happy to work on updating this Python SDK, but in case the generator is being implemented in the next version, there is no need to work on this SDK manually.
🎤 Pitch
At the moment, we are looking for example:
Doing these via the API allows all the console activities to be performed automatically (such as provisioning a new instance). These API endpoints exists already and there is no reason they wouldn't be included in the SDK's.
👀 Have you spent some time to check if this issue has been raised before?
🏢 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: