Laravel · OpenAPI Overlay 1.0.0

API Evangelist conversational phrasing for Laravel Cloud Databases (Legacy) API

6 actions 6 updates phrasing extends openapi/laravel-databases-legacy-api-openapi.yml

Generated by API Evangelist Written by API Evangelist tooling for Laravel's API. It is a proposal applied on top of the contract, not a document Laravel publishes.

View Overlay File View on GitHub Overlay Specification

What the actions change

x-apievangelist-phrasing

Targets 6

$.info

$.paths['/databases'].get

$.paths['/databases'].post

$.paths['/databases/{database}'].get

$.paths['/databases/{database}'].delete

$.paths['/databases/{database}'].patch

OpenAPI Overlay

# Generated by API Evangelist (build-phrasing.py). Our phrasing, not observed demand.
overlay: 1.0.0
info:
  title: API Evangelist conversational phrasing for Laravel Cloud Databases (Legacy) API
  version: 1.0.0
extends: openapi/laravel-databases-legacy-api-openapi.yml
actions:
- target: $.info
  update:
    x-apievangelist-phrasing:
      method: generated
      generated: '2026-10-01'
      generator: build-phrasing.py
      label: Generated by API Evangelist
      operations: 5
- target: $.paths['/databases'].get
  update:
    x-apievangelist-phrasing:
      intent: List databases (deprecated endpoint)
      effect: read
      questions:
      - Can I still list my databases with the older deprecated /databases endpoint?
      - Does the legacy database listing let me filter by type, region or status?
      instructions:
      - text: List my databases using the legacy deprecated endpoint.
      - text: Using the old databases listing, show {type} databases in {region}.
        slots:
          type: query.filter[type]
          region: query.filter[region]
      method: generated
      generated: '2026-10-01'
- target: $.paths['/databases'].post
  update:
    x-apievangelist-phrasing:
      intent: Create a database (deprecated endpoint)
      effect: write
      questions:
      - Is the legacy POST /databases endpoint still usable for creating a database?
      - What does the deprecated create-database call require?
      instructions:
      - text: Create a {type} database named {name} in {region} with config {config} via the deprecated endpoint.
        slots:
          type: requestBody.type
          name: requestBody.name
          region: requestBody.region
          config: requestBody.config
      - text: Use the legacy create call to add database {name} ({type}, {region}, config {config}).
        slots:
          name: requestBody.name
          type: requestBody.type
          region: requestBody.region
          config: requestBody.config
      method: generated
      generated: '2026-10-01'
- target: $.paths['/databases/{database}'].get
  update:
    x-apievangelist-phrasing:
      intent: Get a database (deprecated endpoint)
      effect: read
      questions:
      - Can I look up a database through the deprecated single-database endpoint?
      - What replaces the legacy get-database call?
      instructions:
      - text: Show database {database} using the deprecated endpoint.
        slots:
          database: path.database
      - text: Fetch database {database} through the legacy /databases route.
        slots:
          database: path.database
      method: generated
      generated: '2026-10-01'
- target: $.paths['/databases/{database}'].delete
  update:
    x-apievangelist-phrasing:
      intent: Delete a database (deprecated endpoint)
      effect: destructive
      questions:
      - Can I still delete a database through the deprecated endpoint?
      - Which call should I move to instead of the legacy database delete?
      instructions:
      - text: Delete database {database} via the deprecated endpoint.
        slots:
          database: path.database
      - text: Remove database {database} using the legacy /databases delete.
        slots:
          database: path.database
      method: generated
      generated: '2026-10-01'
- target: $.paths['/databases/{database}'].patch
  update:
    x-apievangelist-phrasing:
      intent: Update a database's config (deprecated endpoint)
      effect: write
      questions:
      - Can I change a database's configuration with the deprecated update call?
      - What does the legacy database update endpoint let me modify?
      instructions:
      - text: Update database {database} config to {config} via the deprecated endpoint.
        slots:
          database: path.database
          config: requestBody.config
      - text: Use the legacy /databases update to set database {database}'s config to {config}.
        slots:
          database: path.database
          config: requestBody.config
      method: generated
      generated: '2026-10-01'