# Generated by API Evangelist (build-phrasing.py). Our phrasing, not observed demand.
overlay: 1.0.0
info:
  title: API Evangelist conversational phrasing for Microsoft Azure Triggers API
  version: 1.0.0
extends: openapi/microsoft-azure-triggers-api-openapi.yml
actions:
- target: $.info
  update:
    x-apievangelist-phrasing:
      method: generated
      generated: '2026-09-26'
      generator: build-phrasing.py
      label: Generated by API Evangelist
      operations: 7
- target: $.paths['/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DataBoxEdge/dataBoxEdgeDevices/{deviceName}/triggers'].get
  update:
    x-apievangelist-phrasing:
      intent: List triggers on a Data Box Edge device
      effect: read
      questions:
      - Which compute triggers are configured on my Data Box Edge device?
      - Can I filter a device's triggers, for example by custom context tag?
      instructions:
      - text: List triggers on Data Box Edge device {deviceName} in {resourceGroupName}, subscription {subscriptionId}.
        slots:
          deviceName: path.deviceName
          resourceGroupName: path.resourceGroupName
          subscriptionId: path.subscriptionId
      - text: Show triggers on device {deviceName} matching {filter}.
        slots:
          deviceName: path.deviceName
          filter: query.$filter
      method: generated
      generated: '2026-09-26'
- target: $.paths['/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DataBoxEdge/dataBoxEdgeDevices/{deviceName}/triggers/{name}'].get
  update:
    x-apievangelist-phrasing:
      intent: Get a trigger on a Data Box Edge device
      effect: read
      questions:
      - How do I see how one trigger on my edge device is configured?
      - What kind of trigger, file event or periodic, is set up on a device?
      instructions:
      - text: Get trigger {name} on Data Box Edge device {deviceName}.
        slots:
          name: path.name
          deviceName: path.deviceName
      - text: Show edge trigger {name} for device {deviceName} in {resourceGroupName}, subscription {subscriptionId}.
        slots:
          name: path.name
          deviceName: path.deviceName
          resourceGroupName: path.resourceGroupName
          subscriptionId: path.subscriptionId
      method: generated
      generated: '2026-09-26'
- target: $.paths['/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DataBoxEdge/dataBoxEdgeDevices/{deviceName}/triggers/{name}'].put
  update:
    x-apievangelist-phrasing:
      intent: Create or update a Data Box Edge trigger
      effect: write
      questions:
      - How do I add a file-event or periodic trigger to a Data Box Edge device?
      - Which trigger kinds does a Data Box Edge device accept?
      instructions:
      - text: Create a {kind} trigger named {name} on device {deviceName}.
        slots:
          kind: requestBody.kind
          name: path.name
          deviceName: path.deviceName
      - text: Update edge trigger {name} on {deviceName} in {resourceGroupName}, subscription {subscriptionId}.
        slots:
          name: path.name
          deviceName: path.deviceName
          resourceGroupName: path.resourceGroupName
          subscriptionId: path.subscriptionId
      method: generated
      generated: '2026-09-26'
- target: $.paths['/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DataBoxEdge/dataBoxEdgeDevices/{deviceName}/triggers/{name}'].delete
  update:
    x-apievangelist-phrasing:
      intent: Delete a trigger from a Data Box Edge device
      effect: destructive
      questions:
      - How do I remove a trigger from my gateway device?
      - Can I delete one Data Box Edge trigger without touching the others?
      instructions:
      - text: Delete trigger {name} from Data Box Edge device {deviceName}.
        slots:
          name: path.name
          deviceName: path.deviceName
      - text: Remove edge trigger {name} on {deviceName} in {resourceGroupName}, subscription {subscriptionId}.
        slots:
          name: path.name
          deviceName: path.deviceName
          resourceGroupName: path.resourceGroupName
          subscriptionId: path.subscriptionId
      method: generated
      generated: '2026-09-26'
- target: $.paths['/datasources/{dataSourceName}/scans/{scanName}/triggers/default'].get
  update:
    x-apievangelist-phrasing:
      intent: Get the schedule trigger of a data source scan
      effect: read
      questions:
      - When is my Purview data source scan scheduled to run?
      - How do I read the trigger set on a data map scan?
      instructions:
      - text: Get the trigger for scan {scanName} on data source {dataSourceName}.
        slots:
          scanName: path.scanName
          dataSourceName: path.dataSourceName
      - text: Show the scan schedule for {scanName} of source {dataSourceName}.
        slots:
          scanName: path.scanName
          dataSourceName: path.dataSourceName
      method: generated
      generated: '2026-09-26'
- target: $.paths['/datasources/{dataSourceName}/scans/{scanName}/triggers/default'].put
  update:
    x-apievangelist-phrasing:
      intent: Schedule a data source scan with a trigger
      effect: write
      questions:
      - How do I set a recurring schedule on a Purview scan?
      - Can I add a trigger so a data source scan runs automatically?
      instructions:
      - text: Create a trigger for scan {scanName} on data source {dataSourceName} with properties {properties}.
        slots:
          scanName: path.scanName
          dataSourceName: path.dataSourceName
          properties: requestBody.properties
      - text: Schedule scan {scanName} of {dataSourceName} to run on a recurrence.
        slots:
          scanName: path.scanName
          dataSourceName: path.dataSourceName
      method: generated
      generated: '2026-09-26'
- target: $.paths['/datasources/{dataSourceName}/scans/{scanName}/triggers/default'].delete
  update:
    x-apievangelist-phrasing:
      intent: Remove the schedule trigger from a scan
      effect: destructive
      questions:
      - How do I stop a Purview scan from running on a schedule?
      - Can I delete the trigger on a data source scan but keep the scan?
      instructions:
      - text: Delete the trigger on scan {scanName} of data source {dataSourceName}.
        slots:
          scanName: path.scanName
          dataSourceName: path.dataSourceName
      - text: Unschedule scan {scanName} for source {dataSourceName}.
        slots:
          scanName: path.scanName
          dataSourceName: path.dataSourceName
      method: generated
      generated: '2026-09-26'