When creating a new database object, the service token(s) don't have access to the newly created db. This might become problematic in cases where eg. data sources need to list databases etc.
One solution to that would be to allow optional automatic requesting to extend the (current) service token's permissions to include the newly created db. However the access should be controllable and possible to fine-tune from the get-go, and this can be solved by providing a list of access rights.
For a full list of access rights on a db, see here: https://api-docs.planetscale.com/reference/service-tokens#database-access-permissions
When creating a new database object, the service token(s) don't have access to the newly created db. This might become problematic in cases where eg. data sources need to list databases etc.
One solution to that would be to allow optional automatic requesting to extend the (current) service token's permissions to include the newly created db. However the access should be controllable and possible to fine-tune from the get-go, and this can be solved by providing a list of access rights.
For a full list of access rights on a db, see here: https://api-docs.planetscale.com/reference/service-tokens#database-access-permissions