Google Cloud Logging · OpenAPI Overlay 1.0.0

API Evangelist conversational phrasing for Google Cloud Logging Sinks API

3 actions 3 updates phrasing extends openapi/google-cloud-logging-sinks-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/{parent}/sinks'].get
$.paths['/v2/{parent}/sinks'].post

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 Sinks API
  version: 1.0.0
extends: openapi/google-cloud-logging-sinks-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/{parent}/sinks'].get
  update:
    x-apievangelist-phrasing:
      intent: List log sinks in a project
      effect: read
      questions:
      - Which sinks are exporting logs out of my project?
      - Can I see all the log routing sinks set up on a folder or organization?
      instructions:
      - text: List every log sink under {parent}.
        slots:
          parent: path.parent
      - text: Show me where {parent} is routing its logs.
        slots:
          parent: path.parent
      method: generated
      generated: '2026-10-01'
- target: $.paths['/v2/{parent}/sinks'].post
  update:
    x-apievangelist-phrasing:
      intent: Create a sink that routes logs to a destination
      effect: write
      questions:
      - Can I export logs that match a filter to BigQuery, Cloud Storage or Pub/Sub?
      - Is it possible for an organization-level sink to include logs from child projects?
      - What does asking for a unique writer identity do when setting up a sink?
      instructions:
      - text: Create sink {name} under {parent} that sends logs to {destination}.
        slots:
          name: requestBody.name
          parent: path.parent
          destination: requestBody.destination
      - text: Route logs matching {filter} from {parent} to {destination} with a new sink.
        slots:
          filter: requestBody.filter
          parent: path.parent
          destination: requestBody.destination
      - text: Create a sink on {parent} that also includes logs from its child projects, sending them to {destination}.
        slots:
          parent: path.parent
          destination: requestBody.destination
      method: generated
      generated: '2026-10-01'