-
Notifications
You must be signed in to change notification settings - Fork 104
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
Unable to find a valid module template to use. #1427
Comments
Can someone help with this please? |
Running with debug shows:
|
FWIW, this is affecting me too. And I get the same output running with |
A temporary workaround is to add the For example: pdk new module foo --template-url=https://github.com/puppetlabs/pdk-templates --template-ref=main |
FWIW: I was able to use the workaround successfully on a Windows 11 workstation, but NOT on a Ubuntu 24.04 instance I tried with both ref options: Not sure what the difference would be, and didn't really take the time to troubleshoot further. Worked fine with previous versions of the PDK in both cases. I'm always willing to assist in providing more relevant details / helping to troubleshoot this if needed on request. EDIT: Perhaps we're looking at a certificate issue as well ... which i thought was taken care of with the update to 3.4.0? And also confirming what was shown above for the git directory traversal problem:
Resolution: Not sure if this is the proper thing to add to the installer/upgrade for PDK though, I'll leave that to others to determine. |
Describe the bug
I get the following error when I run
pdk new module --skip-interview foo /Users/<user>/Workspace/puppet/foo/foo
:I installed the VS Code extension and trying to create a new module using VS Code. Of course, the same command doesn't work from cli. Installed pdk using brew on MacOS.
To Reproduce
Install pdk,
pdk new module --skip-interview foo /Users/<user>/Workspace/puppet/foo/foo
Expected behavior
Should create a module
Additional context
ruby -v
)pdk --version
): 3.4.0The text was updated successfully, but these errors were encountered: