Sign in

Changes to Enable safe migrations for a branch

POST /organizations/{organization}/databases/{database}/branches/{branch}/safe-migrations

Every recorded change to this endpoint, newest first. Back to the operation

Changed in 6 of the 24 revisions of this API.910

  1. 69bdece4890a1
  2. fd44801521102
  3. 4b2e4f05bda24
  4. fa19f33052411
  5. 72506953f36782
  6. 3c33e46f8ff21

What changed

  • 69bdece4890a1See the full diff
    • ▲

      removed the required property deletion_protection_managed from the response with the 200 status

      response-required-property-removed

  • fd44801521102See the full diff
    • ○

      added the required property deletion_protected to the response with the 200 status

      response-required-property-added

    • ○

      added the required property deletion_protection_managed to the response with the 200 status

      response-required-property-added

  • 4b2e4f05bda24See the full diff
    • ○

      added the required property vtgate_autoscaling to the response with the 200 status

      response-required-property-added

    • ○

      added the required property vtgate_max_count to the response with the 200 status

      response-required-property-added

    • ○

      added the required property vtgate_name to the response with the 200 status

      response-required-property-added

    • ○

      added the required property vtgate_target_cpu_utilization to the response with the 200 status

      response-required-property-added

    This revision also has 1 change that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

  • fa19f33052411See the full diff
    • ○

      added the required property keyspace_count to the response with the 200 status

      response-required-property-added

  • 72506953f36782See the full diff
    • ▲

      the response property actor became nullable for the status 200

      response-property-became-nullable

    • ▲

      the response property cluster_iops became nullable for the status 200

      response-property-became-nullable

    • ▲

      the response property deleted_at became nullable for the status 200

      response-property-became-nullable

    • ▲

      the response property parent_branch became nullable for the status 200

      response-property-became-nullable

    • ▲

      the response property restore_checklist_completed_at became nullable for the status 200

      response-property-became-nullable

    • ▲

      the response property restored_from_branch became nullable for the status 200

      response-property-became-nullable

    • ▲

      the response property restored_from_branch/deleted_at became nullable for the status 200

      response-property-became-nullable

    • ▲

      the response property schema_last_updated_at became nullable for the status 200

      response-property-became-nullable

    • ○

      added the required property region/mysql_supported to the response with the 200 status

      response-required-property-added

    • ○

      added the required property region/postgresql_supported to the response with the 200 status

      response-required-property-added

  • 3c33e46f8ff21See the full diff
    • ○

      added the required property vtgate_options to the response with the 200 status

      response-required-property-added