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

Vendor Pull Operation Does Not Work on Windows #832

Open
aclarke822 opened this issue Dec 9, 2024 · 5 comments · Fixed by #856
Open

Vendor Pull Operation Does Not Work on Windows #832

aclarke822 opened this issue Dec 9, 2024 · 5 comments · Fixed by #856
Labels
bug 🐛 An issue with the system

Comments

@aclarke822
Copy link

aclarke822 commented Dec 9, 2024

Describe the Bug

When attempting the vendor pull operation on Windows 11, at least 2 scenarios fail.
With a github source and no version specified, no error is thrown but the resulting directory is empty.
With a github source and a version specified, CreateFile operation fails with:
CreateFile ~\AppData\Local\Temp\1733760752881339476/vpc?ref=1.398.0: The filename, directory name, or volume label syntax is incorrect.

The same scenarios were tested on Amazon Linux (al2023-ami-2023.5.20240722.0-kernel-6.1-x86_64) with no issues.

Expected Behavior

The vendor pull operation should vendor the modules and clone them to the appropriate directories.

Steps to Reproduce

Use the vendor.yaml provided in the quickstart guides and run atmos vendor pull on Windows.

Screenshots

No response

Environment

  • OS: Microsoft Windows 11 Business 10.0.22631 Build 22631
  • Atmos Versions Tested: 1.106.0 / 1.120.0

Additional Context

No response

@aclarke822 aclarke822 added the bug 🐛 An issue with the system label Dec 9, 2024
@osterman
Copy link
Member

osterman commented Dec 9, 2024

We'll look into this, thanks for reporting!

@osterman
Copy link
Member

This should be resolved in 1.128.0

@aclarke822
Copy link
Author

I wanted to come back and say that this scenario still fails:
"With a github source and no version specified, no error is thrown but the resulting directory is empty."

I found that it's tied to the included_paths.
Works:
included_paths: ["**"]
Fails with empty directory:
included_paths: ["**/**.tf"]
For a repo that contains just ./main.tf and ./README.md.

Looks like it could be the same as this issue:
#835

I'll track the other issue for resolution. Thanks again for the quick fix for Windows! 🚀

@osterman osterman reopened this Dec 30, 2024
@osterman
Copy link
Member

osterman commented Dec 30, 2024

@aclarke822 can you confirm the precise version of Atmos you tested?

If you have a vendor config we can use to reproduce (and add to our tests), that will speed it up.

Note, we are now testing on windows in our CI pipelines, so we can confirm vendoring does work in the general sense; there must be something about your configuration we are not testing.

@aclarke822
Copy link
Author

aclarke822 commented Dec 30, 2024

I tested on 1.20.0 and 1.133.0. Here is an example freshly tested on 1.133.0:
https://gist.github.com/aclarke822/c55502591c28c3bd957058916ecd68c8

Files from:
https://github.com/cloudposse/terraform-aws-components/tree/main/modules/vpc

vpcC successfully pulls the files. All other sources appear successful based on CLI output, but result in empty directories. The only difference between them (other than naming) is the included_paths property.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug 🐛 An issue with the system
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants