API Evangelist conversational phrasing for AWS Lambda Concurrency API

# Generated by API Evangelist (build-phrasing.py). Our phrasing, not observed demand.
overlay: 1.0.0
info:
  title: API Evangelist conversational phrasing for AWS Lambda Concurrency API
  version: 1.0.0
extends: openapi/aws-lambda-concurrency-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: 6
- target: $.paths['/2015-03-31/functions/{FunctionName}/concurrency'].get
  update:
    x-apievangelist-phrasing:
      intent: Check a function's reserved concurrency
      effect: read
      questions:
      - How much reserved concurrency does my function currently have?
      - Is there a concurrency cap set on this Lambda function?
      instructions:
      - text: Show the reserved concurrency set on function {function}.
        slots:
          function: path.FunctionName
      - text: Tell me whether {function} has a reserved concurrent execution limit.
        slots:
          function: path.FunctionName
      method: generated
      generated: '2026-10-01'
- target: $.paths['/2015-03-31/functions/{FunctionName}/concurrency'].put
  update:
    x-apievangelist-phrasing:
      intent: Reserve concurrency for a function
      effect: write
      questions:
      - How do I cap the number of simultaneous executions of a Lambda function?
      - Can I reserve part of my account's concurrency so one function is never starved?
      - Does setting reserved concurrency to zero stop a function from running?
      instructions:
      - text: Reserve {count} concurrent executions for function {function}.
        slots:
          function: path.FunctionName
          count: requestBody.ReservedConcurrentExecutions
      - text: Limit {function} to at most {count} simultaneous runs.
        slots:
          function: path.FunctionName
          count: requestBody.ReservedConcurrentExecutions
      method: generated
      generated: '2026-10-01'
- target: $.paths['/2015-03-31/functions/{FunctionName}/concurrency'].delete
  update:
    x-apievangelist-phrasing:
      intent: Remove a function's reserved concurrency limit
      effect: destructive
      questions:
      - How do I take the reserved concurrency limit off a function?
      - What happens to a function's concurrency after its reservation is removed?
      instructions:
      - text: Remove the reserved concurrency limit from function {function}.
        slots:
          function: path.FunctionName
      - text: Let {function} draw on unreserved account concurrency again by clearing its reservation.
        slots:
          function: path.FunctionName
      method: generated
      generated: '2026-10-01'
- target: $.paths['/2015-03-31/functions/{FunctionName}/provisioned-concurrency'].get
  update:
    x-apievangelist-phrasing:
      intent: Check provisioned concurrency on an alias or version
      effect: read
      questions:
      - How many pre-warmed execution environments does my function's alias have?
      - Is provisioned concurrency ready yet on a given version of my function?
      instructions:
      - text: Show the provisioned concurrency config of function {function} for alias or version {qualifier}.
        slots:
          function: path.FunctionName
          qualifier: query.Qualifier
      - text: Check the warm-instance status on {function}:{qualifier}.
        slots:
          function: path.FunctionName
          qualifier: query.Qualifier
      method: generated
      generated: '2026-10-01'
- target: $.paths['/2015-03-31/functions/{FunctionName}/provisioned-concurrency'].put
  update:
    x-apievangelist-phrasing:
      intent: Pre-warm execution environments for an alias
      effect: write
      questions:
      - How do I eliminate cold starts on my production alias?
      - Can I keep a fixed number of Lambda environments initialized for a specific version?
      instructions:
      - text: Provision {count} pre-initialized environments for function {function} on alias {qualifier}.
        slots:
          function: path.FunctionName
          qualifier: query.Qualifier
          count: requestBody.ProvisionedConcurrentExecutions
      - text: Keep {count} warm instances of {function} version {qualifier} ready to respond.
        slots:
          function: path.FunctionName
          qualifier: query.Qualifier
          count: requestBody.ProvisionedConcurrentExecutions
      method: generated
      generated: '2026-10-01'
- target: $.paths['/2015-03-31/functions/{FunctionName}/provisioned-concurrency'].delete
  update:
    x-apievangelist-phrasing:
      intent: Remove provisioned concurrency from an alias
      effect: destructive
      questions:
      - How do I stop paying for pre-warmed environments on an alias I no longer need?
      - Can I drop the provisioned concurrency from one version without touching others?
      instructions:
      - text: Delete the provisioned concurrency config of function {function} for {qualifier}.
        slots:
          function: path.FunctionName
          qualifier: query.Qualifier
      - text: Stop keeping warm instances for {function} alias {qualifier}.
        slots:
          function: path.FunctionName
          qualifier: query.Qualifier
      method: generated
      generated: '2026-10-01'