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
Is your feature request related to a problem?
When working with repos with dependencies on each other, both the terminals of a dependency often need to instantiate each other from within their own codebase. Currently, we do this via profiles. However, this means that the same/similar profile is redefined in multiple places.
e.g. suppose that:
A->B
C ->B
dependency exists. i.e. repo A needs the components from repo B to work, and similarly for C.
This usually means that the profile to deploy B is defined in both A and C.
Ideally, B would provide a profile e.g. -p with-B and that could be used by A, C and any other repo that has B as a dependency.
Which solution do you suggest?
Which alternative solutions exist?
Additional context
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem?
When working with repos with dependencies on each other, both the terminals of a dependency often need to instantiate each other from within their own codebase. Currently, we do this via profiles. However, this means that the same/similar profile is redefined in multiple places.
e.g. suppose that:
A->B
C ->B
dependency exists. i.e. repo A needs the components from repo B to work, and similarly for C.
This usually means that the profile to deploy B is defined in both A and C.
Ideally, B would provide a profile e.g.
-p with-B
and that could be used by A, C and any other repo that has B as a dependency.Which solution do you suggest?
Which alternative solutions exist?
Additional context
The text was updated successfully, but these errors were encountered: