(Issue #4,#9,#10,#11) Fix confine rest-client as a feature within the provider

Branch: Herr-Herner/puppet-module-nexus_rest:fix_confine_restclient

Branch: atlassian/puppet-module-nexus_rest:master

Merged

#49 · Created 2015-11-12 · Last updated 2015-11-25

Merged pull request

Merged in Herr-Herner/puppet-module-nexus_rest/fix_confine_restclient (pull request #49)

74865da·Author: Martin Meinhold·Closed by: Martin Meinhold·2015-11-25

Description

A fix that (hopefully) solves Issue #4, #9, #10 and #11. It allows Puppet to apply resources from the nexus_rest module when the rest-client gem gets installed in the same run.

I have made same testings under Ubuntu Server 14.04 with Puppet 4.2.3. At the moment I cannot test the fix with Puppet 3.x

With Puppet 4:

package { 'rest-client':
  ensure => 'present',
  provider => 'puppet_gem',
} ->
nexus_repository { 'new-repository':
  label => 'A New Repository',
  provider_type => 'maven2',
  type => 'hosted',
  require => Service['nexus']
}

(Issue #4,#9,#10,#11) Fix confine rest-client as a feature within the provider

Merged pull request

Description

0 attachments

0 comments

Loading commits...