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? Please describe.
Shallow clones can cause issues with Zarf because it expects to mirror a repository and a shallow clone does not contain all of the object references in that repository.
Describe the solution you'd like
Detect the object not found error on a git push in in the push() function (
For anyone that might hit this issue in the interim (referencing the cloned repo within a pipeline build for your zarf.yaml), the workaround in Gitlab is to specify the below in your .gitlab-ci.yml pipeline configuration. This disables shallow cloning.
Is your feature request related to a problem? Please describe.
Shallow clones can cause issues with Zarf because it expects to mirror a repository and a shallow clone does not contain all of the object references in that repository.
Describe the solution you'd like
Detect the
object not found
error on a git push in in thepush()
function (zarf/src/internal/packager/git/push.go
Line 157 in 182a4df
Additionally add a
:::caution
admonition to the git-data example that describes that a user should not use shallow clones with Zarf linking them to a page like this for more information: https://github.blog/2020-12-21-get-up-to-speed-with-partial-clone-and-shallow-cloneAdditional context
For more information see: https://kubernetes.slack.com/archives/C03B6BJAUJ3/p1683743369646829
The text was updated successfully, but these errors were encountered: