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
We have a git repository with several submodules. How to configure Fleet NOT to make git submodule update? With current SSH keys provided to Fleet, it does not have access to those submodules thus making container step-git-source to fail. There's no need for Fleet to have access to any of those submodules. It should be possible to configure Fleet not to update submodules. Is this already possible?
The text was updated successfully, but these errors were encountered:
I'm currently running into an issue similar to @patrijua. I'm trying to rollout a gitrepo, that has multiple submodules from other git hosts, which gitcloner is not allowed to reach. When cloning the repo, gitcloner runs into a timeout, when recursively cloning the modules.
I don't think it is currently possible to override this behaviour, since #2557 was merged. Gitcloner uses the default recursion depth, without a way to override this setting.
We have a git repository with several submodules. How to configure Fleet NOT to make git submodule update? With current SSH keys provided to Fleet, it does not have access to those submodules thus making container step-git-source to fail. There's no need for Fleet to have access to any of those submodules. It should be possible to configure Fleet not to update submodules. Is this already possible?
The text was updated successfully, but these errors were encountered: