test(smoke): give the smoke-aws-docs fixture a readiness probe #107
@@ -12,6 +12,19 @@ servers:
|
||||
env:
|
||||
- name: FASTMCP_LOG_LEVEL
|
||||
value: "ERROR"
|
||||
# Mirrors the production `aws-docs` probe. Without it this fixture is a
|
||||
# RUNNING server with no readiness probe, so it fails the very assertion in
|
||||
# health-readiness.smoke.test.ts that the fixture exists to support — the
|
||||
# suite reporting its own scaffolding as a fleet regression.
|
||||
# `search_documentation` needs a phrase; the 300s interval matches aws-docs,
|
||||
# since the call leaves the cluster.
|
||||
healthCheck:
|
||||
tool: search_documentation
|
||||
arguments:
|
||||
search_phrase: "s3 bucket"
|
||||
timeoutSeconds: 20
|
||||
intervalSeconds: 300
|
||||
failureThreshold: 3
|
||||
|
||||
projects:
|
||||
- name: smoke-data
|
||||
|
||||
Reference in New Issue
Block a user