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

Puppet 4 is more strict with facts scripts #60

Open
ubellavance opened this issue Jul 4, 2017 · 1 comment
Open

Puppet 4 is more strict with facts scripts #60

ubellavance opened this issue Jul 4, 2017 · 1 comment

Comments

@ubellavance
Copy link
Contributor

When I tested the module with Puppet 4, it wouldn't work. I can't remember exactly but it's either because php is not present when called first (that is why I rewrote some scripts in python) or because the scripts returned nothing.

There must be a way to comply by doing an if file exists then run the API call, if not return what Puppet would like.

@mkherlakian Please assign the puppet4 label

@ubellavance
Copy link
Contributor Author

It's because the interpreter in the shebang doesn't exist on the first puppet run. Logs:

Error: Facter: error while processing "/opt/puppetlabs/puppet/cache/facts.d/get_application_details.php" for external facts: child process returned non-zero exit status (2).
Error: Facter: error while processing "/opt/puppetlabs/puppet/cache/facts.d/get_vhost_details.php" for external facts: child process returned non-zero exit status (2).
Error: Facter: error while processing "/opt/puppetlabs/puppet/cache/facts.d/get_library_details.php" for external facts: child process returned non-zero exit status (2).

I think the only solution is to write them in a language that is installed by default on all distros... most likely python.

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

1 participant