Google Cloud Logging · OpenAPI Overlay 1.0.0

API Evangelist conversational phrasing for Google Cloud Logging API

3 actions 3 updates phrasing extends openapi/google-cloud-logging-google-cloud-logging-api-api-openapi.yml
Generated by API Evangelist Written by API Evangelist tooling for Google Cloud Logging's API. It is a proposal applied on top of the contract, not a document Google Cloud Logging publishes.
View Overlay File View on GitHub Overlay Specification

What the actions change

x-apievangelist-phrasing

Targets 3

$.info
$.paths['/v2/{sinkName}'].get
$.paths['/v2/{sinkName}'].delete

OpenAPI Overlay

Raw ↑ 
# Generated by API Evangelist (build-phrasing.py). Our phrasing, not observed demand.
overlay: 1.0.0
info:
  title: API Evangelist conversational phrasing for Google Cloud Logging API
  version: 1.0.0
extends: openapi/google-cloud-logging-google-cloud-logging-api-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: 2
- target: $.paths['/v2/{sinkName}'].get
  update:
    x-apievangelist-phrasing:
      intent: Look up a log sink's configuration
      effect: read
      questions:
      - Where is a particular log sink routing my logs to?
      - Can I check the filter and destination of one sink by its name?
      instructions:
      - text: Show me the configuration of sink {sinkName}.
        slots:
          sinkName: path.sinkName
      - text: Tell me the destination and filter of log sink {sinkName}.
        slots:
          sinkName: path.sinkName
      method: generated
      generated: '2026-10-01'
- target: $.paths['/v2/{sinkName}'].delete
  update:
    x-apievangelist-phrasing:
      intent: Delete a log sink
      effect: destructive
      questions:
      - Can I stop exporting logs by removing a sink?
      - What happens to log routing once I delete a sink?
      instructions:
      - text: Delete log sink {sinkName}.
        slots:
          sinkName: path.sinkName
      - text: Remove sink {sinkName} so it no longer routes logs.
        slots:
          sinkName: path.sinkName
      method: generated
      generated: '2026-10-01'