Hi all, we've started landing changes for what will become Puppet Platform 6.
Here's the News You Can Use relating to the release.
Scope and Timeline
We expect to release it in the fall, and the major features of the release are
currently scoped to be:
- improved secret and ephemeral data handl
Thanks. I found that adding "require 'parseconfig'" to the
spec/spec_helper.rb file also allows the tests to run. bundle exec is
failing with dependency errors as well.
On Monday, April 23, 2018 at 5:24:08 PM UTC-4, Garrett Honeycutt wrote:
>
> On 4/23/18 4:38 PM, Michael Watters wrote:
> >
On 4/23/18 4:38 PM, Michael Watters wrote:
> Has anybody used rspec-puppet to run tests using a function that
> requires external ruby gems? I'm running unit tests on resources that
> call functions in the puppet_thycotic module however rspec is failing
> with an error as shown below.
>
> Failure
Has anybody used rspec-puppet to run tests using a function that requires
external ruby gems? I'm running unit tests on resources that call
functions in the puppet_thycotic module however rspec is failing with an
error as shown below.
Failure/Error: require 'parseconfig'
Puppet::Pre
Use the puppetlabs-mysql module to manage the grants for each user/db. You
can have different values for each environment stored in hiera.
On Friday, April 20, 2018 at 11:42:22 AM UTC-4, Jonathan Preston wrote:
>
> I've searched for answers, but couldn't find anything quite matching my
> use ca
Hello guys.
Just out of the oven, a module that helps you to design and update the
certificates generated by the site https://www.sslforfree.com/.
Through this site you can have access to a valid certificate for a host or
an entire domain for free. This site uses the "let's encrypt" API.
But bec
refreshonly and notify are your friends.
file { 'zipfile':
notify Exec['unzip'],
source => 'file:///downloads/someZipFile.zip'
}
exec { 'unzip zipfile -d /some/file':
alias => 'unzip',
refreshonly => true,
notify => Exec['installer']
}
exec { '/some/file/setup.exe /a':
alias => 'ins
jcbollinger has it right. You're setting environment variables, and then
exiting the environment.
Here's what is effectively happening:
# bash
# source ./opensh.rc
echo $OS_TOKEN
fbed3beb36960f2b3e1b
# exit
# echo $OS_TOKEN
#
When you tell Puppet to do an exec, it spawns a new instance of th
hello John, thanks for the answer!!!
This problem only happens in linux machines that are in the domain, because
I have not yet tested on windows.
Linux machines names in the test:
- mint-client.mycompany.intra
- ubuntu-client.mycompany.intra
Use the 'certname' setting in your machines' Puppet
Hello John / Chris,
First of all, I’d like to thank both of you for taking out time and
providing your valuable inputs on this topic. I am extremely sorry if my
query was not clear enough.
I am trying to set up a keystone (Identity server) for openstack.
content of openrc.sh file:
--
On Sunday, April 22, 2018 at 2:26:11 AM UTC-5, Justin tim wrote:
>
> Hi,
>
> I've been trying to setup openstack keystone for my DEV environment using
> Puppet. Everything works fine, except the 'exec' resource.
>
> I have tried the below things, but not getting the desired results
>
> 1. '*/bi
On 23/04/18 08:33, Johan De Wit wrote:
first notify, the index should be quoted
notify { "OS: $facts['os']['family']": }
That us unfortunately wrong - it will produce the entire $facts hash as
a string followed by the *text* "['os']['family']".
The correct way is to write:
notify {
12 matches
Mail list logo
