fix database API compatibility - #205
Conversation
Cloud rejects deprecated include=schemas requests and serves HTML for the obsolete plural restore endpoint.
|
Confirming this reproduces on a clean v0.5.2 install (macOS, Same 400 from We depend on |
The CLI still used the deprecated
schemasrelationship for database cluster requests. Laravel Cloud rejects these requests because the accepted include isdatabases.The database restore request also used the obsolete plural
/restoresendpoint. This route returned the Laravel Cloud HTML page with HTTP 200 instead of an API response. The current API uses the singular/restoreendpoint.This change:
include=databasesfor all database cluster requestsA live point-in-time restore completed the request successfully and returned a new cluster with
restoringstatus.API reference: https://laravel.com/cloud/docs/api/database-restores/create-a-database-restore
Tests
vendor/bin/pest tests/Feature/DatabaseClusterDeleteTest.php tests/Feature/DatabaseClusterListTest.php tests/Feature/DatabaseRestoreCreateTest.phpvendor/bin/pint --testvendor/bin/phpstan analyse --no-progress