Skip to content

fix(azure-openai-java): document released legacy setup - #1049

Merged
nik13 merged 3 commits into
mainfrom
fix/azure-openai-java-released-legacy-guide
Nov 4, 2026
Merged

nik13 merged 3 commits into
mainfrom
fix/azure-openai-java-released-legacy-guide

Conversation

@nik13

@nik13 nik13 commented Oct 31, 2026

Copy link
Copy Markdown
Contributor

Summary

Correct the Azure OpenAI section of the Java provider guide for the already-released legacy wrapper.

  • Replace JitPack main-SNAPSHOT with Maven Central com.futureagi:traceai-java-azure-openai:1.0.0.
  • Explicitly include com.azure:azure-ai-openai:1.0.0-beta.16, because the wrapper declares the SDK as provided.
  • Use the application's deployment name instead of assuming it equals a model name; show shutdown for the short-lived example.
  • State the actual three blocking methods and the untraced streaming/async/unwrap boundary.
  • Link Microsoft's maintenance notice and avoid promising that the shared OpenAI wrapper is an equivalent Azure migration.
  • Add two guide regression tests to the existing integration CI suite.

This page works with packages already on Maven Central and does not depend on an unreleased traceAI change. It does not advertise new streaming or async support. Other providers on this shared page are unchanged.

Validation

  • Before: both new guide tests fail against the base section. After: all 11 integration/scaffolding tests pass.
  • Extracted the Java snippet verbatim, placed it in a main method, and compiled it against freshly downloaded Maven Central artifacts in an isolated Maven repository.
  • Six real-Azure-SDK tests pass against released wrapper 1.0.0 using synthetic in-process HTTP responses; no vendor/model calls or real credentials. The supported floor and current Azure SDK are both beta.16.
  • npm run build: Astro and Pagefind pass.
  • npm run audit-links: zero broken navigation/content links; 28 existing orphan pages.
  • Desktop Chrome rendered the Azure installation, example, and support table at 1440px; inspected both screenshots. This is a docs rendering check, not a claim of live Azure or Future AGI execution.
  • Tests/build/browser checks ran with outbound networking denied except localhost.
  • Standards self-review: no introduced blocking finding; no API/contract/migration change. E2E coverage: not applicable (no product e2e/ harness).

No merge or publication performed.

Generated with Claude Code

nik13 and others added 3 commits October 31, 2026 06:16
Use Central coordinates and the explicit Azure SDK dependency. Limit the guide to supported blocking calls and explain the upstream maintenance and migration boundary.

Co-Authored-By: Claude Code <noreply@anthropic.com>
Co-Authored-By: Claude Code <noreply@anthropic.com>
Document the released gen_ai attributes and raw serialization limitation. Exercise the exact Maven and Gradle snippets against synthetic Azure and captured OTLP on Java 17 and 21.

Co-Authored-By: Claude Code <noreply@anthropic.com>
@nik13
nik13 merged commit 4815166 into main Nov 4, 2026
8 checks passed
@nik13
nik13 deleted the fix/azure-openai-java-released-legacy-guide branch November 4, 2026 12:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant