Thanks Luke. I guess like anyone using Puppet, Gary is always a good starting
point (I have certainly quoted some of his material in practice presentations I
have given internally). I had read this one including the Q around roles and
profiles, but it was so long ago that I had forgotten, so
Thanks Josh, that did the trick on both Linux and Windows.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view
Puppet Version: 4.3.1
OS: Centos 7
Note: I am running MASTERLESS
I used this to install a gem :-
package { 'rubyzip':
ensure => present,
provider => 'gem',
}
It installed fine, in this location :
/usr/local/share/gems/gems/rubyzip-1.1.7
gem env shows that the parent folder is on
Personally I try to avoid putting hiera calls in manifests since this can
make debugging significantly harder not to mention potentially clouding the
intent of that module/class. I prefer exposing the data needs of a module
via its API (i.e. class parameters) which also helps to make its intent
I guess having a single module containing all possible profile classes is one
way to go. So in this case you just have a single Git repo called profiles,
right, and as/when the need for a new combination of resource modules arises,
would just add a new class for that purpose to this module ?
I
Been using the Roles and Profiles pattern for a while, but only recently
had the need to create a Profile that is required in a number of Roles.
Typically we use Git sub-modules when we want to do this sort of thing, but
I don't want to make this a discussion about Git sub-modules vs. other
Puppet: 4.2.1
OS: RHEL/Centos 7 (can also simulate on Windows if I set osfamily to
'RedHat')
Most of the time I develop Puppet modules to run only on Windows but
sometimes I want them to be able usable on other OS's particularly RHEL.
Sometimes there's a choice between adding a bunch of
layout on line 4
Fraser.
On Sunday, 20 December 2015 08:47:25 UTC, Fraser Goffin wrote:
>
> Puppet: 4.2.1
> OS: RHEL/Centos 7 (can also simulate on Windows if I set osfamily to
> 'RedHat')
>
> Most of the time I develop Puppet modules to run only on Windows but
> sometimes I
Hey Martin,
arrgghh, you are right of course, good shout. All working now.
In the version of Stdlib I'm using the function is actually called 'downcase'.
Regards
Fraser.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from
Gave it a shot tonight with a masterless Puppet set up and it appears to
work ok (just like your own module-data module)
metadata.json (note:data_provider)
{
"name": "goffinf-lookuptest",
"version": "0.1.0",
"author": "goffinf",
"summary": "Test of Puppet 4 lookup experimental feature",
Puppet: 4.2.1
Facter: 3.0.2
OS: Windows
I have a module with a facts.d folder containing a simple yaml file and a
powershell script :-
sonatype_nexus
- puppet
- modules
- sonatype_nexus
- facts.d
facts.yaml
Yep, will do. Since the folder names are created by the Puppet provisioner in
the tmp directory as was the case for earlier versions (which worked
successfully) perhaps it's has been introduced with the later version of Puppet
and Facter or there is now an underlying incompatibility between
Jira ticket :-
Module level external facts not resolved when using the Vagrant Puppet
provider : https://tickets.puppetlabs.com/browse/FACT-1276
On Friday, 13 November 2015 18:48:48 UTC, Peter Huene wrote:
>
> Hi Fraser,
>
> On Fri, Nov 13, 2015 at 10:00 AM, Fraser Goffin <g
Hey Josh,
Thanks for the heads up. You are right, version 0.4.3 does propose a solution
to this but unfortunately in my testing it doesn't quite work. I have raised a
couple of additional issues so with any luck Atlassian will sort it out
sometime soon. So still using the 2 run work-around for
Puppet v 4.2.x
Platform: Windows
I'm using the Atlassian sonatype_nexus Puppet module. It allows you to
configure Nexus via its RESTful API using a number of abstractions from the
module. However, ... there is a requirement for a few additional Ruby gems
to be installed, the key one being a
Puppet: v4.2.1
Hiera: v3.0.1
Facter: v3.0.2
Ruby: 2.1.6p336
Platform: Windows.
Came across an interesting behaviour when using hiera that was unexpected
(to me anyway). I don't necessarily think its a bug, but I thought it worth
sharing for others who may come across it. Keep in mind that this
Whilst there are definitely some uses cases where executing scripts in either
Powershell or via an Exec resource is the way to go, in my opinion you should
really be thinking of using the higher level resource abstractions. That way
you don't need to deal with the implementation details and you
Yes, thanks for the comment. I am aware of this approach, but given the module
still works ok under Puppet4 and we have a used it a fair bit, I (and my
bosses) would obviously prefer not to have to develop a new solution. That
said, it is something I am looking into.
Fraser.
--
You received
Forgot to mention, this also worked successfully with Vagrant 1.7.2 and Puppet
3.x, but upgrades to both are where we are today.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it,
For some time I have been using the excellent ripienaar/puppet-module-data
module. This provides a very familiar way to use Hiera but at the individual
module level.
I have recently upgrade to Puppet v4 and this module still works successfully
when run with 'puppet apply' (I am using
For the benefit of others, I contacted the maintainer of the reidmv/unzip
module and this was his (very helpful) response :-
Hi Fraser,
The requirement that the file be local is just a constraint of how the unzip
module works right now. This is a very simple module. In practice, that means
I have been trying out a couple of modules that provide the ability to unzip on
Windows (reidmv/unzip and counsel/puppet-windows).
Both of these work, indeed it would appear using a similar approach (powershell
using .Copyhere). However both of them appear to require that the source zip
file
Caveat: I know nothing about your specific infrastructure and application stack
setup or how you manage it or the suitability of the business apps you have
deployed or .. Well you get the idea, but in a VM world, wouldn't you
prefer following the immutable server pattern, then uninstalls
Here's a simple example that works for me :-
First you obviously have the ripienaar/module_data module installed and
available to your puppet apply (I'm using masterless puppet).
My folder structure :-
- puppet
| modules
|--- sonarqube
|-- data
|- hiera.yaml
Hi,
I am attempting to use the puppetlabs/concat module on Windows, but having
some problems. To keep things really simple since it illustrates the
problem, here is the mainfest I'm using (note: it just uses concat at this
stage) :-
class concat_file {
concat {
25 matches
Mail list logo
