Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question: Possibility to ignore git submodules? #586

Closed
patrijua opened this issue Nov 1, 2021 · 3 comments
Closed

Question: Possibility to ignore git submodules? #586

patrijua opened this issue Nov 1, 2021 · 3 comments

Comments

@patrijua
Copy link

patrijua commented Nov 1, 2021

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?

@nickgerace
Copy link
Contributor

nickgerace commented Nov 1, 2021

I think the resolution of the following issue would solve this one: #583

@kkaempf
Copy link
Collaborator

kkaempf commented Jan 3, 2023

see #583

@kkaempf kkaempf closed this as not planned Won't fix, can't repro, duplicate, stale Jan 3, 2023
@zube zube bot closed this as completed Jan 3, 2023
@zube zube bot removed the [zube]: Done label Apr 4, 2023
@niklastreml
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants