feat(dependency): Adding dependency management to commands #56
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adding the first layer of dependency management to commands. This includes pulling in one level of remote dependencies for services. What this means is that when running
start
, we first find and install any required remote dependencies for the given service. All other commands that rely on docker compose first check to see if the dependencies exist locally (as they should) since we want to re-use the same dependencies we installed/updated when we ranstart
. There are potential edge-cases where the service may have been started but the dependencies don't exist locally (not sure how this would happen yet, but it's likely possible). In this case, we have a basic fallback to simply re-install the dependencies, which while not ideal, since the dependencies could have been updated since running start, it is a good initial mitigation effort that we can further improve down the road.