Hello out there simple question, new to puppet world! I would like to verify lines, if not present add lines at the end in the config file. I have to check following lines in the location : /etc/screenrc

bindkey "^D" echo 'Blocked. Please use [Ctrl]+[A] + [Ctrl]+[Enter] + [Y]'
bind "^M" quit

How to adopt in below manifest file or any different way? Thanks

file {'/etc/screenrc':
    ensure => 'file',
  }
  file_line {'':
    path    => '/etc/screenrc',
    line    => '',
    require => File['/etc/screenrc'],
  }

Yes, you are likely correct about globs. In my

facter -p

output, I still see the following, even though I have

memory.swap.used*

in the blocklist:

memory => {
  swap => {
    available_bytes => 3883233280,
    total => "4.00 GiB",
    total_bytes => 4294963200,
    used_bytes => 411729920
  },
  system => {
    available_bytes => 1616789504,
    total => "11.43 GiB",
    total_bytes => 12273041408,
    used_bytes => 10656251904
  }
}

That's right. I changed the globs to individual items:

"memory.swap.used"
"memory.swap.used_bytes"

And the output from

facter -p

changed to:

memory => {
  swap => {
    available => "3.62 GiB",
    total => "4.00 GiB",
    total_bytes => 4294963200
  },
  system => {
    available => "1.51 GiB",
    total => "11.43 GiB",
    total_bytes => 12273041408
  }
}

That's right. I replaced the globs with individual items:

"memory.swap.used"
"memory.swap.used_bytes"

And the output from

facter -p

changed to:

memory => {
  swap => {
    available => "3.62 GiB",
    total => "4.00 GiB",
    total_bytes => 4294963200
  },
  system => {
    available => "1.51 GiB",
    total => "11.43 GiB",
    total_bytes => 12273041408
  }
}

That's right. I replaced the globs with individual items:

"memory.swap.used"
"memory.swap.used_bytes"

and the output from

facter -p

changed to:

memory => {
  swap => {
    available => "3.62 GiB",
    total => "4.00 GiB",
    total_bytes => 4294963200
  },
  system => {
    available => "1.51 GiB",
    total => "11.43 GiB",
    total_bytes => 12273041408
  }
}

That's right. I replaced the globs with individual items:

"memory.system.used",
"memory.system.used_bytes",
"memory.swap.used",
"memory.swap.used_bytes",

and the output from

facter -p

changed to:

memory => {
  swap => {
    available => "3.62 GiB",
    total => "4.00 GiB",
    total_bytes => 4294963200
  },
  system => {
    available => "1.51 GiB",
    total => "11.43 GiB",
    total_bytes => 12273041408
  }
}

@Sergei G.: Since puppet is not a monitoring system and I don't care about ephemeral facts, I have the following in

/etc/puppetlabs/facter/facter.conf

to block unwanted facts:

facts : {
  blocklist : [
    "file system",
    "load_averages",
    "identity",
    "memory.system.capacity",
    "memory.system.used",
    "memory.system.used_bytes",
    "memory.system.available",
    "memory.system.available_bytes",
    "memory.swap.capacity",
    "memory.swap.used",
    "memory.swap.used_bytes",
    "memory.swap.available",
    "memory.swap.available_bytes",
    "system_uptime",
  ]
}

Hope that helps.

That's right. I replaced the globs with individual items:

"memory.system.used",
"memory.system.used_bytes",
"memory.swap.used",
"memory.swap.used_bytes",

and the output from

facter -p

changed to:

memory => {
  swap => {
    available => "3.62 GiB",
    total => "4.00 GiB",
    total_bytes => 4294963200
  },
  system => {
    available => "1.51 GiB",
    total => "11.43 GiB",
    total_bytes => 12273041408
  }
}

and you can see

used

and

used_bytes

is no longer there.

Thanks. That looks good. So I suspect the problem then is that the code you've written there isn't the code that's being applied. Can you show a couple of the lines below that red error message in the screenshot you posted earlier? That'll tell me where in the Puppet code the offending resource is coming from.

Also, on that node that's failing its Puppet run, please run this as root and show me the result:

facter os

message has been deleted

stepped on something new in puppet7, another warning

warning:[Puppet]: Fact value '#!/bin/bash
...
with the value length: '4772' exceeds the value length limit: 4096

I think fact name instead of the whole value printed in log would be more useful. especially since that fact can have a sensitive data

in this case ec2_userdata is a culprit

Hello out there simple question, new to puppet world! I would like to verify lines, if not present add lines at the end in the config file. I have to check following lines in the location : /etc/screenrc

bindkey "^D" echo 'Blocked. Please use [Ctrl]+[A] + [Ctrl]+[Enter] + [Y]'
bind "^M" quit

How to adopt in below manifest file or any different way? Thanks

file { '/etc/screenrc':
  ensure  => file,
  content => "hello\nworld\n",
}

message has been deleted

message has been deleted

Hello out there simple question, new to puppet world! I would like to verify lines, if not present add lines at the end in the config file. I have to check following lines in the location : /etc/screenrc

defscrollback 30000
bindkey "^C" echo 'Blocked. Please use [Ctrl]+[A] + [Ctrl]+[Enter] + [Y]'
bindkey "^D" echo 'Blocked. Please use [Ctrl]+[A] + [Ctrl]+[Enter] + [Y]'
bind "^M" quit

How to adopt in below manifest file or any different way? Thanks

file { '/etc/screenrc':
  ensure => file,
  append => "defscrollback 30000\nbindkey \"^C\" echo 'Blocked. Please use [Ctrl]+[A] + [Ctrl]+[Enter] + [Y]'\nbindkey \"^D\" echo 'Blocked. Please use [Ctrl]+[A] + [Ctrl]+[Enter] + [Y]'\nbind \"^M\" quit\n",
}

This message was deleted.

This message was deleted.

hello out there, Below manifest added content in the file at end.

$contents = file('/etc/screenrc')

$new_contents = "${contents}defscrollback 30000\nbindkey \"^C\" echo 'Blocked. Please use [Ctrl]+[A] + [Ctrl]+[Enter] + [Y]'\nbindkey \"^D\" echo 'Blocked. Please use [Ctrl]+[A] + [Ctrl]+[Enter] + [Y]'\nbind \"^M\" quit\n"

file { '/etc/screenrc':
  content  => $new_contents,
  ensure => file,
}

Output:

# #shelltitle ' |zsh'
# #shelltitle '> |csh'
# #shelltitle '$ |bash'
defscrollback 30000
bindkey "^C" echo 'Blocked. Please use [Ctrl]+[A] + [Ctrl]+[Enter] + [Y]'
bindkey "^D" echo 'Blocked. Please use [Ctrl]+[A] + [Ctrl]+[Enter] + [Y]'
bind "^M" quit

But when running manifest file again, then content added two times, how to prevent this or something to verify if same content there not add it again. thanks

This message was deleted.

That's right. I replaced the globs with individual items:

"memory.system.used",
"memory.system.used_bytes",
"memory.swap.used",
"memory.swap.used_bytes",

and the output from

facter -p

changed to:

memory => {
  swap => {
    available => "3.62 GiB",
    total => "4.00 GiB",
    total_bytes => 4294963200
  },
  system => {
    available => "1.51 GiB",
    total => "11.43 GiB",
    total_bytes => 12273041408
  }
}

and you can see

used

and

used_bytes

are no longer there.

This message was deleted.

@helindbe thanks for your suggestions above, I ended up using the Enum as below as i could not get the

any

to work:

unless (Enum[$k] in $valid_sections) {
        fail("Invalid section '${k}' in '${key}' hash. Verify the section is valid and in correct CaSe")
      }

Hello, I'm trying to to set a sensitive value in an epp following https://www.puppet.com/docs/puppet/7/lang_template_epp.html#epp_variables-epp-sensitive-data and I am not able to do it. Basically every time I try to use

scope

in the template I get the following error (it doesn't matter if it has

::sensitive

or not, I always get the same error):

Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: A substring operation does not accept a String as a character index. Expected an Integer

It doesn't matter if I pass the variables as parameters of the

epp

function in the manifest, or if I use the name with the full scope of the variable, I get also the same error). The only way I can make it work is with the

$::module::variable

syntax (or

$variable

if I pass it as a parameter) but then I can't mark the value as sensitive in the epp template. Anyone can give me a hand with this please 🙂 ? (I'm using Puppet 7 too)

This message was deleted.

Hey I'll raise a doc ticket to correct this, I would make the variable sensitive in the Puppet manifest and just pass it in like any other parameter since as of 6.20 EPP will unwrap sensitive values automatically. Scope was an ERB thing and shouldn't need to be used in EPP

This message was deleted.

This message was deleted.

file { '/etc/screenrc':
  content => file("${module_name}/configs/screenrc"),
}

and put the file at files/configs/screenrc in your module