Today, we released Puppet agent 1.10.5.
This release includes mostly bug fixes for Puppet and Facter, and adds
package support for a few new platforms.
Read the Puppet agent 1.10.5 release notes:
https://docs.puppet.com/puppet/4.10/release_notes_agent.html#puppet-agent-1105
Read the Puppet
It could, I don't know. I'm new to Puppet so installing PuppetDB as a
module before Puppet Server was installed was very confusing starting out.
I ended up writing a Bash script following Andrew Grimberg's flow.
Thanks
On Sunday, July 23, 2017 at 2:27:17 AM UTC-7, Lowe Schmidt wrote:
>
>
I ended up having to do the same thing. Thanks for the guidance!
On Monday, July 24, 2017 at 6:37:23 AM UTC-7, Andrew Grimberg wrote:
>
> On 07/22/2017 09:50 AM, Keith Miller wrote:
> > Hey guys, new to Puppet and looking for some help. Some facts first:
> >
> > * Using Ubuntu 16.04
> >
Hello I am a newbie with puppet
I am trying to take a module I cobbled together to run a script
class mymodule::myscript {
file {
'myscript':
ensure => 'file',
source => 'puppet:///modules/mymodule/myscript.sh',
path => '/usr/local/bin/myscript.sh',
owner => 'root'
Hi Jonathan,
You can use the PuppetDB CLI to do queries
directly. https://docs.puppet.com/puppetdb/5.0/pdb_client_tools.html
- Russ
On Wednesday, July 26, 2017 at 3:57:37 AM UTC-7, Jonathan Gazeley wrote:
>
> Hi folks,
>
> I'm trying to troubleshoot an issue about tagging and realising
On 21/07/17 08:39, Vikram Varma wrote:
Hi All,
I am getting the following error wheile running "puppet apply -v
d:\default.pp"
Error: Could not autoload puppet/type/dism: Attempt to redefine method
set_present with block
Error: Evaluation Error: Error while evaluating a Resource Statement,
On 24/07/17 22:37, Siva nagi reddy wrote:
Hi,
We had setup Puppet enterprise master agent environment to deploy one
application. We setup non-root user account by following Puppet dcos to
deploy application as we dont have permissions for root account.
1) Installed the Sample module
And sometimes it turns out the answer is obvious in retrospect once one's error
has been posted up in public. I was doing:
file { '/tmp/tt2':
content => template('test1/two.epp'),
}
When I actually invoke an epp template like I should, it works.
file { '/tmp/tt2':
content =>
Would somebody mind passing a spare clue regarding the correct syntax?
I already know this works in an erb template:
<%= scope.call_function('test1::test1', ['input one!!']) %>
However this fails in an epp template:
<%= test1::test1('input two!!') %>
Unfortunately, that's about as far as I
Hi folks,
I'm trying to troubleshoot an issue about tagging and realising exported
resources. Is there a way I can browse/view exported resources in
PuppetDB to make sure the expected tags have been applied?
Thanks,
Jonathan
--
You received this message because you are subscribed to the
Thanks Peter,
I have created manifest to get details
On Tuesday, July 25, 2017 at 8:29:31 PM UTC+5:30, Amber Mehra wrote:
>
> Hey Guys,
>
> I have certain requirement to get puppet client inventory like "facter
> operatingsystem, facter ipaddress, etc : copied all details to some where
> in
11 matches
Mail list logo
