Test: Validate HTTP runtime targets #82

Objective

Validate that AgentOps works against non-Foundry deployed targets over HTTP, covering runtime portability.

Scope

Exercise the HTTP backend using the documented starter configs for model, RAG, or agent-with-tools over endpoint.kind: http. The current docs support HTTP targets for model and agent scenarios, including AKS and Container Apps hosting, with dedicated starter configs such as run-http-model.yaml, run-http-rag.yaml, and run-http-agent-tools.yaml.

Tasks

• Pick one deployed HTTP target
• Configure URL and request/response field mappings
• Run at least one model-style scenario and one agent-style scenario if feasible
• Verify authentication and payload mapping behavior
• Execute agentops eval run
• Review results and identify HTTP-specific friction points
• Log issues related to config, auth, docs, and troubleshooting

Acceptance Criteria

• At least one HTTP target can be evaluated successfully
• Request/response field mapping is well understood
• Differences between Foundry and HTTP execution are documented
• Runtime portability gaps are captured as backlog items
• The team has a clear recommendation for future HTTP examples

Out of Scope

• Load testing the deployed endpoint
• Supporting every authentication variant
• Refactoring the HTTP backend in this sprint