Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/pages/configuration/imports/README.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -50,7 +50,7 @@ The following table clarifies when to use `imports` and when to use `dependencie
| Difference | `imports` | `dependencies` |
| ---------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Use Case | Importing shared/standardized functionality (e.g. `functions`, `pipelines`, `commands`) into **independent** projects | Defining logical dependencies between **inter-dependent** projects (app A requiring app B to be deployed) |
| Example | If projects A and B should both have some shared functionality that is defined in a shared `devspace.yaml` | If a project A with requires projectd B and C to be deployed in order to work correctly |
| Example | If projects A and B should both have some shared functionality that is defined in a shared `devspace.yaml` | If a project A with requires projects B and C to be deployed in order to work correctly |
| Impact | If project A imports a `devspace.yaml` from another `devspace.yaml`, then everything defined in this imported `devspace.yaml` will be merged into the `devspace.yaml` of project A. | If project A has a `devspace.yaml` that defines project B as a git-based `dependency`, then DevSpace will `git clone` project B and deploy it when you run `run_dependency_pipelines b` inside your pipeline script. |


Expand Down