Can't admin user, project and api key programmatically while configuring a test env for E2E test
- 0
- Self Hosted
- General
- Web
- REST API
Hi there, I’ve been trying to setup a test environment for my project to support tests at all levels of the test pyramid including unit, integration and end to end tests. After doing some research I have to spin up a local appwrite instance for my tests. I’ve managed to spin up the local instance. However, I’m having some concerns with how the setup and teardown of the testing environment. There is no way for me to create an admin user, organisation, project and project api key (with scopes) so that I can the server sdk except through the console ( user interface ). Therefore, I’d like to inquire whether there’s any way to automate this because it would be handy during setup and teardown of my test environment. If that cannot work, I’d like an alternative approach. I've done some research about the console SDK but unfortunately it isn't available for appwrite
Recommended threads
- Error upgrading from 1.8.1 to 1.9.0
DO Self-hosted server failed to upgrade with this error "Error response from daemon: client version 1.52 is too new. Maximum supported API version is 1.42". U...
- MariaDB refuses to connect to appwrite
Earlier, I tried updating my Appwrite version from 18.1.x to the latest release because my Flutter package required it to function properly. I used the official...
- Custom API domain is unreachable
Earlier my custom api domain was working fine. Now it seems to be offline without a trace a few hours later. I didn't change anything, all the relevant DNS reco...