API Evangelist conversational phrasing for Microsoft Azure Manifest API

# 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 Manifest API
  version: 1.0.0
extends: openapi/microsoft-azure-manifest-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: 5
- target: $.paths['/v2/{name}/manifests/{reference}'].get
  update:
    x-apievangelist-phrasing:
      intent: Pull a container image manifest
      effect: read
      questions:
      - How do I fetch the manifest for an image in my container registry?
      - Can I pull a manifest by digest instead of by tag?
      instructions:
      - text: Get the manifest for image {name} at reference {reference}.
        slots:
          name: path.name
          reference: path.reference
      - text: Pull manifest {reference} of repository {name} as media type {accept}.
        slots:
          reference: path.reference
          name: path.name
          accept: header.accept
      method: generated
      generated: '2026-09-26'
- target: $.paths['/v2/{name}/manifests/{reference}'].put
  update:
    x-apievangelist-phrasing:
      intent: Push a container image manifest
      effect: write
      questions:
      - How do I upload an image manifest to my container registry?
      - Can I tag an image by putting its manifest under a new reference?
      instructions:
      - text: Put the manifest {payload} for repository {name} at reference {reference}.
        slots:
          payload: body.payload
          name: path.name
          reference: path.reference
      - text: Push a manifest to image {name} tagged {reference}.
        slots:
          name: path.name
          reference: path.reference
      method: generated
      generated: '2026-09-26'
- target: $.paths['/v2/{name}/manifests/{reference}'].delete
  update:
    x-apievangelist-phrasing:
      intent: Delete a container image manifest
      effect: destructive
      questions:
      - How do I delete an image manifest from my registry?
      - Why can a manifest only be deleted by digest and not by tag?
      instructions:
      - text: Delete the manifest of repository {name} with digest {reference}.
        slots:
          name: path.name
          reference: path.reference
      - text: Remove image {name} manifest {reference} from the registry.
        slots:
          name: path.name
          reference: path.reference
      method: generated
      generated: '2026-09-26'
- target: $.paths['/subscriptions/{subscriptionId}/providers/Microsoft.ProviderHub/providerRegistrations/{providerNamespace}/generateManifest'].post
  update:
    x-apievangelist-phrasing:
      intent: Generate a resource provider manifest
      effect: write
      questions:
      - How do I generate the manifest for my ProviderHub resource provider?
      - Can I produce a provider manifest from its current registration?
      instructions:
      - text: Generate the manifest for provider namespace {providerNamespace}.
        slots:
          providerNamespace: path.providerNamespace
      - text: Build the ProviderHub manifest for {providerNamespace}.
        slots:
          providerNamespace: path.providerNamespace
      method: generated
      generated: '2026-09-26'
- target: $.paths['/subscriptions/{subscriptionId}/providers/Microsoft.ProviderHub/providerRegistrations/{providerNamespace}/checkinManifest'].post
  update:
    x-apievangelist-phrasing:
      intent: Check in a resource provider manifest
      effect: write
      questions:
      - How do I check in my resource provider's manifest to an environment?
      - What baseline ARM manifest location is needed to check in a provider manifest?
      instructions:
      - text: Check in the manifest for {providerNamespace} to environment {environment} from baseline {baselineArmManifestLocation}.
        slots:
          providerNamespace: path.providerNamespace
          environment: requestBody.environment
          baselineArmManifestLocation: requestBody.baselineArmManifestLocation
      - text: Check in provider {providerNamespace} manifest to {environment}.
        slots:
          providerNamespace: path.providerNamespace
          environment: requestBody.environment
      method: generated
      generated: '2026-09-26'