Repository navigation
[Automated] Draft docs (kagent): chore: remove unsupported Azure OpenAI inline token configuration - #731
Open
github-actions[bot] wants to merge 1 commit into
Open
[Automated] Draft docs (kagent): chore: remove unsupported Azure OpenAI inline token configuration#731github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
…AI inline token configuration Signed-off-by: GitHub Action <action@github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
kagent-dev/kagent#3651 — chore: remove unsupported Azure OpenAI inline token configuration
Docs versions:
mainNo code-path rule covers 1 touched file(s). The planner could route these only by identifier search, so the candidate pages may miss what they changed, including in the other mode:
go/core/pkg/env/providers.goWhat changes for users:
azureAdTokenis no longer available on ModelConfig for Azure OpenAI. Users must use an API key Secret, token passthrough, oractorJwtcredentials instead of setting an inline Microsoft Entra ID token.What the docs now say: The Azure OpenAI provider page no longer lists
azureAdTokenas a provider setting or authentication option. Its authentication section now states thatazureAdTokenis not available in ModelConfig and points readers to the supported credential configurations.How
kagent-3651was draftedPlan, and what changed it
azureAdTokenauthentication option from the Azure OpenAI provider guide.latest, but the work-list authorizes onlymainand generated references are covered byupdate-ref-docs.yaml.docs-site/content/kagent/main/setup/model-providers/azure-openai.md.Why a documentation change is necessary
The pull request removes
azureAdTokenfrom the ModelConfig Go type, the CRD schema, Helm values, the runtime translation path, and the UI provider optional parameters. The Azure OpenAI guide listedazureAdTokenas a provider setting and as an authentication configuration, so a reader could try to configure a field that the current API no longer serves. The generatedmain/reference/api-ref.mdandmain/reference/helm.mdpages still show stale rows in this checkout, but the work-list marks those pages as generated reference output.How to verify this change
setup/model-providers/azure-openai.md. The API server accepts the resource.azureAdTokenunderspec.azureOpenAIin that ModelConfig, then runkubectl apply --dry-run=server --validate=strict -f <file>. The API server reports thatspec.azureOpenAI.azureAdTokenis unknown.kubectl explain modelconfig.spec.azureOpenAI.azureAdToken. The command reports that the field does not exist.Proposed release note
No
proposed-release-note.md:markers.notes_placeableis false for this repository. The dossier release-note text is: RemoveazureAdTokenfromModelConfigbecause the kagent runtime does not consume the emittedAZURE_AD_TOKENvalue, and it bypasses v1's gateway credential injection approach.Files in this pull request
docs-site/content/kagent/main/setup/model-providers/azure-openai.mdHow the pages were chosen (triage report)
Feature clusters
Kept apart on purpose. Merging wrongly produces a guide that documents two things and explains neither, so these are reported for a person to merge rather than grouped automatically:
docs-site/content/kagent/main/agents/agent-harness.mdas a candidate, but for one of them it is one page among more than 3, so they are kept apart; merge them if both drafts do land theredocs-site/content/kagent/main/agents/agent-harness.mdas a candidate, but for one of them it is one page among more than 3, so they are kept apart; merge them if both drafts do land thereDraft a documentation change
kagent-dev/kagent#3651 — chore: remove unsupported Azure OpenAI inline token configuration
kagent-dev/websiteazureAdTokenfromModelConfigbecause the Kagent runtime does not consume the emittedAZURE_AD_TOKENvalue, and it bypasses v1's gateways credential injection approach.go/core/pkg/env/providers.goDraft branch:
pr-tracker-draft-kagent-3651