v2.1.208

Features

App Installation Patch

• Added support for patching app installations, including a new field to specify desired changes to linked databases. This allows developers to address specific database configurations directly when updating app installations.

Backup Modifications

• Refactored backup operations to include new deprecated routes. Introduced new response types for deprecated backup expiration time and project update descriptions, facilitating smoother transitions for clients using outdated methods.

Container Stack Updates

• Updated container client methods to reflect deprecations and provide alternatives for setting stack update schedules, enhancing the API's usability.

Bug Fixes and Improvements

• Fixed response handling in the App client for patch requests, ensuring appropriate responses for 400 errors.
• Refactored various backup operations to handle legacy requests properly, streamlining interaction and improving error handling across deprecated endpoints.
• Resolved inconsistencies in how the responses are structured across newly deprecated endpoints, ensuring a unified and expected output.

Project Notifications

• Cleaned up the responses related to project notification thresholds, consolidating response objects for better clarity and reduced complexity. This change affects how clients initialize and respond to project update requests.

Deprecations

• Several backup methods and endpoints have been deprecated in favor of newer, improved alternatives. These deprecations are documented, and clients are encouraged to transition to the recommended endpoints for enhanced stability and support.