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

"pdk convert" and "pdk new module" fails on OSX Sierra #396

Closed
natemccurdy opened this issue Dec 19, 2017 · 4 comments
Closed

"pdk convert" and "pdk new module" fails on OSX Sierra #396

natemccurdy opened this issue Dec 19, 2017 · 4 comments

Comments

@natemccurdy
Copy link
Contributor

natemccurdy commented Dec 19, 2017

PDK: 1.3.0
OS: OSX Sierra 10.12

When doing a pdk convert in an existing module or when creating a new module, I get the following error:

pdk (ERROR):
pdk (ERROR): fatal: ambiguous argument '1.3.0': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'

pdk (FATAL): Unable to set git repository '/var/folders/ss/b33hxsf54bx0rbg0gqjd1yr40000gq/T/pdk-templates20171219-99977-154j6im' to ref:'1.3.0'.
@natemccurdy natemccurdy changed the title pdk convert fails on OSX Sierra "pdk convert" and "pdk new module" fails on OSX Sierra Dec 19, 2017
@natemccurdy
Copy link
Contributor Author

The git repo at that path in /var/folders has a remote that points to:

https://github.com/puppetlabs/pdk-module-template

That repo does not have a tag for 1.3.0.

Seems like that template repo should be https://github.com/puppetlabs/pdk-templates instead

@natemccurdy
Copy link
Contributor Author

The culprit was ~/.pdk/cache/answers.json that contained the old templates repo URL. Deleting that json file fixed the problem.

But, an upgrade to 1.3.0 from an older version should handle that more cleanly.

Thanks for the help @scotje !

@scotje
Copy link
Contributor

scotje commented Dec 19, 2017

Created https://tickets.puppetlabs.com/browse/PDK-736 to track a more complete fix for this.

@natemccurdy
Copy link
Contributor Author

Looks like this is resolved in #397

I'll close this ticket. Thanks!

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

No branches or pull requests

2 participants