-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Gitlab repo download fails #651
Comments
Thanks for the raising the issue. The Gitlab support is less than robust, so I'm not wholly surprised. I'll take a look and see what I can do. |
awesome thanks! Please let me know if I can grab any other logs or anything else |
We've run into this as well - it would appear that the directory name inside the tarball may have changed to be |
leg100
pushed a commit
that referenced
this issue
Dec 6, 2023
This was a small change we had to make for solving the issue with #651 wherein we see a different name structure for the directory within the tarball that we get from gitlab
Merged
leg100
added a commit
that referenced
this issue
Dec 12, 2023
leg100
pushed a commit
that referenced
this issue
Dec 12, 2023
🤖 I have created a release *beep* *boop* --- ## [0.2.3](v0.2.2...v0.2.3) (2023-12-12) ### Bug Fixes * gitlab support ([#665](#665)) ([eaf9b15](eaf9b15)), closes [#651](#651) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
I am on otf 0.1.18 running docker containers on nomad with projects on gitlab, When I attempt a plan or apply with VCS now it fails with
"retrieving repository tarball: malformed directory name found in tarball"
and
:ERROR constructing new run error="retrieving repository tarball: malformed directory name found in tarball: cloudflare-main-***" subject="
The text was updated successfully, but these errors were encountered: