Skip to content

Feat/resource dependencies - #3353

Open
neelneelneel wants to merge 4 commits into
devfrom
feat/resource-dependencies
Open

neelneelneel wants to merge 4 commits into
devfrom
feat/resource-dependencies

Conversation

@neelneelneel

Copy link
Copy Markdown
Contributor

Description

Adds catalog dependencies for both engines and projects. Dependencies come in two kinds: automatic ones, recorded from an item's configuration when it's saved, and manual ones that users add. This PR also adds an admin-only Dependency Map that shows every engine, project and link on the platform as one interactive graph.

Changes Made

  • Engine and project dependencies: engines can now have dependencies, not just projects (engine-to-engine and engine-to-project). Reads and writes go through GetCatalogDependencies / SetCatalogDependencies.
  • Automatic dependencies: when an item is saved, the backend records links from its configuration. Examples: an agent's model, skills, toolboxes and knowledge; a model's guardrails; a vector DB's embedder; a router's routes; an automation's nodes; a blocks app's engines; code references. Each link has a role. They're read-only in the UI, and a save only replaces the manual links.
  • Manual dependencies: each can have an optional name (unique per owner) and a description. Links saved before this change come back as manual.
  • Shared client feature: features/catalog/dependencies/ holds the dependencies view, the edit dialog and the Engines panel, used by both projects and engines. It replaces edit-project-dependencies-dialog and the old project dependencies page. Engines get a new Dependencies tab.
  • Permission propagation: propagateUserPermissions is now propagateCatalogDependencyPermissions(catalogId, catalogType?) and works for both engines and projects.
  • Dependency Map: a new admin page at Settings → Dependency Map (settings/dependencies).
    • The backend works out where every node goes (AdminGetCatalogDependencyGraph). The client just draws it with React Flow.
    • Views: All, Trace (what an item uses or what uses it, both directions, up to a depth, with impact counts) and User Access (what one user can reach, and which links they can't follow).
    • Search, type and link filters, a legend, and a details drawer with links to Resource Governance.
    • The current view is kept in the URL, so it can be shared. There's also a full-screen expand mode.
    • Sync (AdminBackfillCatalogDependencies) rebuilds automatic dependencies for existing items.
  • Tests and docs: tests for the dependency model, the graph, the view state and the API. packages/client/AGENTS.md is updated.

How to Test

  1. Open an agent or app → Dependencies. Check that config-driven links show as automatic (role badge, can't edit). Add, rename and remove a manual dependency and save. Automatic links should stay, and duplicate names should be rejected.
  2. Change the agent's model or skills and save. Its automatic dependencies should update.
  3. Open an engine → Dependencies tab. Add an engine or project as a dependency. It should save and reload.
  4. As an admin, open Settings → Dependency Map:
    • Run Sync. You should see counts per kind and a list of any failures, then the map reloads.
    • Search for an item and click it. The drawer should show Overview, Uses, Used by and Security.
    • Switch to Trace, change the direction and depth, and check that the impact counts change.
    • Switch to User Access, pick a user, and turn on "show gaps". Links the user can't follow should be marked.
    • Copy the URL into a new tab. The same view should open.
    • Check Expand, then Escape: the first Escape closes the drawer, the next one closes the expanded view.
  5. A non-admin should not see the Dependency Map tile.

Notes

  • The backend, UI and any other dependent repos need to be deployed together. The pixel names have changed (propagateProjectDependencyPermissions → propagateCatalogDependencyPermissions, plus new admin graph, access and backfill reactors).
  • Run Sync once after deploying, so existing items get their automatic dependencies.
  • GetCatalogDependents exists on the backend but the client doesn't use it yet.
  • The map is reached only from its Settings tile.

neelneelneel and others added 4 commits November 17, 2026 13:26
Conflicts resolved:
- The create/upload/export reactors only conflicted on line endings
  (this branch had rewritten them with LF). Each now takes dev's file
  with its CRLF endings plus this branch's dependency changes.
  CreateGuardrailEngineReactor keeps dev's
  setDefaultEngineMarkdown(user, ...) and adds the dependency sync
  after it.
- SecurityEngineUtils / SecurityProjectUtils delete lists: remove the
  item's CATALOGDEPENDENCIES rows plus dev's ENGINE2ENGINEPERMISSION
  rows (dev drops PROJECTENGINEPERMISSION).
- SecurityProjectUtils: keep this branch's removal of the
  PROJECTDEPENDENCIES methods (now SecurityCatalogDependencyUtils);
  dev's only change there was write-access checks, which
  SetCatalogDependencies already does.
- SecurityOwlCreator: CATALOGDEPENDENCIES with IS_AUTOMATIC, ROLE,
  NAME and DESCRIPTION, documented in dev's table-comment style.
- Tests: deleteEngine now takes the user.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@neelneelneel
neelneelneel requested a review from a team as a code owner November 20, 2026 00:33
@snyk-io

snyk-io Bot commented Nov 20, 2026

Copy link
Copy Markdown
Contributor

✅ Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
✅ Open Source Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@neelneelneel

Copy link
Copy Markdown
Contributor Author

Dependent on SEMOSS/semoss-ui#3918
Dependent on SEMOSS/Monolith#489
Dependent on #3353

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