Hi @natemccurdy. How are you? The data doesnt load in Foreman. A shortened version of the data appears in Foreman like this:

@natemccurdy - Now if I try to save and send that longer data it doesn't appear

Hi @natemccurdy. How are you? The data doesnt load in Foreman. A shortened version of the data appears in Foreman like this given I save the file in a shortened number of rows

well no its not truncated. If I save say only a few rows in the file, it uploads.

message has been deleted

Gonna see if I can generate a much smaller installed software list. The PowerShell script I use grabs everything in registry. Only really need general listing from Programs in Control Panel

message has been deleted

Hello, I’ve noticed that when the puppetdb docker image is updated and the container restarted with the new image, the reports are wiped from the postgres database. Why is that happening and is there a way to retain data? It’s not wiped when a container is just restarted with the same image, only when the image changes. Is this likely to be something wrong in the docker-compose config?

This message was deleted.

Yeah, it's a benign error. The setting it's controlling does get set, it's just that the YAML parser that extension is using is being extra strict.

Ah, here you go: https://github.com/redhat-developer/vscode-yaml/issues/392#issuecomment-727412143

no idea. I just go to the extensions's gear icon and click "Extension Settings" Then, under "Yaml: Custom Tags", click "Edit in settings.json"

message has been deleted

message has been deleted

JFYI, you can write the rsyslog config in this way:

# Handle messages as specified.
if $programname == 'ucarp' then {
action(type="omfile" file="/var/log/ucarp.log")
# Send messages to the configured remote via TCP.
action(type="omfwd" target="127.0.0.1" port="11514")
stop
}

This way you don’t need those “&” at all. This syntax is more-or-less available in any rsyslog 8.x (and even in some latest 7.x IIRC).

JFYI, you can write the rsyslog config in this way:

if $syslogfacility-text =='local5' then {
# Write it to the local file
action(type="omfile" file="/var/log/ucarp.log")
# Send it to the specified target via the specified proto
action(type="omfwd" target="127.0.0.1" port="11514" protocol="tcp")
# Drop it here
stop
}

This way you don’t need those “&” at all. This syntax is more-or-less available in any rsyslog 8.x (and even in some latest 7.x IIRC).

JFYI, you can write the rsyslog config in this way:

if $syslogfacility-text =='local5' then {
# Write it to the local file
action(type="omfile" file="/var/log/local5.log")
# Send it to the specified target via the specified proto
action(type="omfwd" target="127.0.0.1" port="11514" protocol="tcp")
# Drop it here
stop
}

This way you don’t need those “&” at all. This syntax is more-or-less available in any rsyslog 8.x (and even in some latest 7.x IIRC).

Please check the EditorConfig: 1. https://editorconfig.org/ 2. https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig 3. https://github.com/voxpupuli/puppet-chrony/blob/master/.editorconfig

This message was deleted.

For a puppetfile, is there a way to have it prefer a specific "test" branch by default for a given environment?

that way one doesn't need to edit the puppetfile before merging to production?

that way one doesn't need to edit the puppetfile before merging to production?

https://puppet.com/docs/pe/2019.8/puppetfile.html#declare_content_from_a_relative_control_repo_branch (if your module has branches that match your control repository)

oooh I like it

message has been deleted

This message was deleted.

i.e. if you have no Foreman it’ll still work this way with pure OSS Puppet

easiest way to test is e.g.

file { '/tmp/packages.txt': content => $facts['software'] }

easiest way to test is e.g.

file { '/tmp/packages.txt': content => $facts.get('software') }