Skip to content
This repository has been archived by the owner on Jun 11, 2019. It is now read-only.

Issue with locking PHP to particular version #44

Open
liquorvicar opened this issue Jan 17, 2014 · 2 comments
Open

Issue with locking PHP to particular version #44

liquorvicar opened this issue Jan 17, 2014 · 2 comments

Comments

@liquorvicar
Copy link

We had an issue recently where we were trying to lock PHP to a specific point release. It worked fine when that was the latest version in the repo but as soon as the repo released a new version it broke. To fix it we had to specify the version for each and every module we were using. Is this the intended behaviour in this scenario? Or should the Php::Module define use $php::version by default? I'm happy to create a pull request if necessary...

@karibis
Copy link

karibis commented Oct 8, 2014

Liquorvicar, do you have a pull request available for this issue? Or have you fixed this local?
I tried your suggestion to set the php version in hiera per node and included that parameter in my global php profile but that does not work. As soon as my yum repo has a new php version php gets updated to the latest version. Using version 2.0.18 of this module.

Any help or suggestions are appreciated.

@liquorvicar
Copy link
Author

No, I never got as far as a pull request for this.

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

No branches or pull requests

2 participants