Skip to content

fix: correct repository directory reference in ontology deployment - #81

Merged
Yamini Dhiman (Yamini1-Microsoft) merged 1 commit into
devfrom
psl-graph-fix
Aug 7, 2026
Merged

fix: correct repository directory reference in ontology deployment#81
Yamini Dhiman (Yamini1-Microsoft) merged 1 commit into
devfrom
psl-graph-fix

Conversation

@Yamini1-Microsoft

Copy link
Copy Markdown
Contributor

Purpose

This pull request includes a small but important change to the ontology deployment process in the fabric_solution_installer.ipynb notebook. The change ensures that the repository_directory parameter is explicitly converted to a string when deploying ontologies, which can help prevent potential type errors.

Does this introduce a breaking change?

  • Yes
  • No

Golden Path Validation

  • I have tested the primary workflows (the "golden path") to ensure they function correctly without errors.

Deployment Validation

  • I have validated the deployment process successfully and all services are running as expected with this change.

What to Check

Verify that the following are valid

  • Validate if the graph for ontology in Fabric workspace is showing all nodes and relationship correctly.
  • Validate if Fabric data agent is answering questions correctly.

Other Information

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the Fabric solution installer notebook’s ontology deployment to pass the workspace-scoped repository path (explicitly cast to str) into deploy_ontology, aligning ontology discovery with the artifacts directory used for Fabric deployments.

Changes:

  • Update the deploy_ontology(...) call to use repository_directory=str(workspace_directory) instead of repo_root_directory.

@Yamini1-Microsoft
Yamini Dhiman (Yamini1-Microsoft) merged commit 0b8a20b into dev Aug 7, 2026
6 of 8 checks passed
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.

3 participants