release: v3.4.3#557
Merged
Merged
Conversation
…552) scripts/postProvision.ps1::Set-GptRagAppConfiguration explicitly seeded every FOUNDRY_IQ_* App Configuration key but left the WORK_IQ_* and FABRIC_IQ_* keys (added in v3.3.0 and v3.4.0) to be populated as a side-effect of config/search/setup.py rendering search.settings.j2. That meant operators enabling Work IQ or Fabric IQ post-provision had to know the exact key names, run �z appconfig kv set for each key, and then re-run the search setup script. Extend the seeding block with the matching Get-OptionalEnvValue calls and the same defaults as search.settings.j2 (�nabled=false, everything else \\\`) so a fresh provision registers the keys with their defaults and operators can flip them from the App Configuration blade. Fixes #551 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Adds parallel Fabric Data Agent (fabricDataAgent) knowledge source support alongside Work IQ and Fabric ontology. Feature is opt-in via FABRIC_DATA_AGENT_ENABLED and defaults off. - search.j2: emit fabricDataAgent KS + KB reference when enabled. - search.settings.j2: expose four FABRIC_DATA_AGENT_* keys. - setup.py: add is_fabric_data_agent_enabled helper. - postProvision.ps1: seed the four new keys with defaults. - Tests: 4 new tests, all 25 pass. - manifest.json: bump orchestrator pin to v3.4.0 for paired retrieve support. - CHANGELOG: Unreleased entry. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Bump manifest.json orchestrator pin from v3.4.0 to v3.4.1 to actually ship the Fabric Data Agent knowledge source support advertised in v3.4.2. The FDA retrieve wiring (kind=fabricDataAgent, per-user OBO forwarding, dataAgentAnswer normalization) landed on the orchestrator's develop branch a few minutes after v3.4.0 was tagged, so the container built from v3.4.0 had no code path to consume the Foundry IQ knowledge source that v3.4.2's platform templates were registering. Add v3.4.3 entry to CHANGELOG explaining the mismatch and the fix. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
⛔ Pull requests to
|
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
1 participant
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.
Release v3.4.3.
Why
v3.4.2advertised Fabric Data Agent (Microsoft Fabric) knowledge source support, but pinnedmanifest.jsonorchestrator atv3.4.0, and the FDA retrieve wiring (kind=fabricDataAgent, per-user OBO forwarding,dataAgentAnswernormalization) actually landed on the orchestrator'sdevelopbranch a few minutes AFTER thev3.4.0tag was cut.Live Azure validation with
FABRIC_DATA_AGENT_ENABLED=true+ stub GUIDs confirmed:PUT knowledgesources/fabric-data-agent-ks-stubagainst Foundry IQ2026-05-01-previewreturned201 Created.FABRIC_DATA_AGENTsymbols insrc/connectors/foundry_iq.py. Nokind=fabricDataAgententry ever gets appended toknowledgeSourceParamsat retrieve time.Net result:
v3.4.2deployments that flipped the feature on had the knowledge source registered in Foundry IQ but no actual Fabric Data Agent grounding happening at retrieval time.What
manifest.json: orchestrator pinv3.4.0->v3.4.1(which carries the FDA retrieve code).manifest.json: platformtagv3.4.2->v3.4.3.CHANGELOG.md: addv3.4.3section explaining the fix.No template, script, or App Configuration changes. Existing
v3.4.2environments only need to redeploy the orchestrator container to pick up the fix.Validation
[\uFFFD\u0000-\u0008\u000B\u000C\u000E-\u001F\u2014]onmanifest.json,CHANGELOG.md, and PR body: 0 matches.v3.4.2validation run: App Config keys seeded correctly,search.j2rendered the FDA KS block with stub GUIDs, Foundry IQ registered the KS successfully.tests/test_foundry_iq_fabric_data_agent.py) cover the FDA retrieve code path.v3.4.1is the same one that was expected to ship in orchestratorv3.4.0per the platformv3.4.2release notes.