Dependency Management
Foundry apps consist of multiple artifacts (functions, integrations, collections, workflows, UI extensions) that can depend on each other. Foundry tracks these dependencies and warns you when changes may break connected components.
Dependency types
Section titled “Dependency types”| Type | Description |
|---|---|
| App-internal | Dependencies between artifacts within the same app. For example, a workflow that calls a function, or a UI extension that reads from a collection. |
| External | Dependencies on CrowdStrike platform capabilities (API scopes, LogScale repositories) or external APIs configured through integrations. |
Breaking changes
Section titled “Breaking changes”A breaking change is any modification to an artifact that may cause dependent artifacts to fail. Examples:
- Removing or renaming a function that a workflow calls
- Changing a collection schema in a way that invalidates existing data
- Removing an API integration operation that a workflow action uses
- Changing a function’s request or response format
When you attempt to deploy a change that introduces a breaking dependency, Foundry warns you and identifies the affected artifacts. You must resolve the conflicts before deployment succeeds.
No-dependency artifacts
Section titled “No-dependency artifacts”Some artifacts have no dependencies and can be freely modified:
- Standalone queries that aren’t referenced by workflows or dashboards
- RTR scripts that aren’t called from workflows
- UI extensions that don’t call functions or read collections
Resolving dependency conflicts
Section titled “Resolving dependency conflicts”When Foundry identifies a breaking change:
- Review the list of affected artifacts.
- Update the dependent artifacts to accommodate the change.
- Deploy all changes together so dependencies are resolved atomically.