You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| 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) |
53
-
| 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 |
53
+
| 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 |
54
54
| 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. |
0 commit comments