Devspace deploy do not git pull for cached dependencies
What happened?
As part of this PR https://github.com/devspace-sh/devspace/pull/2709 i introduced a regression bug where it now never attempts to git pull for cached dependencies.
I have created a PR https://github.com/devspace-sh/devspace/pull/2766 to revert this with some refactoring.
What did you expect to happen instead?
Given the configuration
dependencies:
dependency-a:
git: https://www.somewhere.com/dependency-a
branch: master
disablePull: false
I expect devspace deploy to pull new commits to dependency-a that has happen since the last devspace deploy.
Local Environment:
- DevSpace Version: 6.3.5
- Operating System: windows
- ARCH of the OS: AMD64 Kubernetes Cluster:
- Cloud Provider: kind
- Kubernetes Version: 1.27.2
Anything else we need to know?
Read https://github.com/devspace-sh/devspace/pull/2766
PR: https://github.com/devspace-sh/devspace/pull/2766
I'm running into this as well. Interestingly, devspace update dependencies doesn't work either:
❯ devspace update dependencies
#######################################################
################## devspace update ####################
#######################################################
Usage:
devspace update [command]
Available Commands:
plugin Updates a devspace plugin
Flags:
-h, --help help for update
Global Flags:
--debug Prints the stack trace if an error occurs
--disable-profile-activation If true will ignore all profile activations
--inactivity-timeout int Minutes the current user is inactive (no mouse or keyboard interaction) until DevSpace will exit automatically. 0 to disable. Only supported on windows and mac operating systems
--kube-context string The kubernetes context to use
--kubeconfig string The kubeconfig path to use
-n, --namespace string The kubernetes namespace to use
--no-colors Do not show color highlighting in log output. This avoids invisible output with different terminal background colors
--no-warn If true does not show any warning when deploying into a different namespace or kube-context than before
--override-name string If specified will override the DevSpace project name provided in the devspace.yaml
-p, --profile strings The DevSpace profiles to apply. Multiple profiles are applied in the order they are specified
--silent Run in silent mode and prevents any devspace log output except panics & fatals
-s, --switch-context Switches and uses the last kube context and namespace that was used to deploy the DevSpace project
--var strings Variables to override during execution (e.g. --var=MYVAR=MYVALUE)
Use "devspace update [command] --help" for more information about a command.
Is this related? hope to see your PR merged soon!
@aiguofer - Use devspace reset dependencies to delete the cached dependencies, so they are redownloaded next time to devspace deploy.