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

What needs to be done to make this puppet 4 ready? #175

Closed
ghost opened this issue Nov 13, 2015 · 5 comments
Closed

What needs to be done to make this puppet 4 ready? #175

ghost opened this issue Nov 13, 2015 · 5 comments
Labels
needs-feedback Further information is requested

Comments

@ghost
Copy link

ghost commented Nov 13, 2015

If ready, update metadata.json

@juniorsysadmin
Copy link
Member

The unit tests currently test against Puppet 4/Ruby 2.1.6 and some time ago I applied this module with Puppet 4 on an Ubuntu 14.04 agent (puppetserver-2.1.1/puppet-agent-1.2.1). What is the issue you're facing?

@juniorsysadmin juniorsysadmin added the needs-feedback Further information is requested label Nov 16, 2015
@ghost
Copy link
Author

ghost commented Nov 16, 2015

I was looking at the dependencies in the metadata.json and puppet 4 support
wasn't explicit
https:/puppet-community/puppet-nodejs/blob/master/metadata.json#L65

On Mon, Nov 16, 2015 at 6:51 AM, Ben S [email protected] wrote:

The unit tests currently test against Puppet 4/Ruby 2.1.6 and some time
ago I applied this module with Puppet 4 on an Ubuntu 14.04 agent
(puppetserver-2.1.1/puppet-agent-1.2.1). What is the issue you're facing?


Reply to this email directly or view it on GitHub
#175 (comment)
.

Dennis Paskorz | Developer, EotY

Wall-to-Wall Studios, Inc.
1010 Western Avenue, Suite 302, Pittsburgh, PA 15233
T 412 232 0880 | F 412 232 0906
W www.walltowall.com

@igalic
Copy link
Contributor

igalic commented Nov 17, 2015

@pskrz would you like to provide a patch for that?

@ghost
Copy link
Author

ghost commented Nov 18, 2015

@igalic I set up a patch to update the version requirement, but perhaps the travis builds shouldn't allow failure for "Ruby: 2.1.6 PUPPET_GEM_VERSION="~> 4.0" STRICT_VARIABLES="yes" ":

screen shot 2015-11-18 at 8 49 59 am

@igalic
Copy link
Contributor

igalic commented Nov 18, 2015

perhaps it's time to put this module under modulesync control…

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-feedback Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants