This message was deleted.

got lots of questions this morning. 🙂 , does anyone know why the following rule was removed from auth.conf when upgrading to puppet 7

{
            match-request: {
                path: "/puppet/v3/status"
                type: path
                method: get
            }
            allow-unauthenticated: true
            sort-order: 500
            name: "puppetlabs status"
        },

Its the Puppet analytics service which checks things like in the case are you at the latest version. You can find out more and opt out of this following the guide at https://puppet.com/docs/pe/2021.6/analytics_overview.html#analytics_opt_out_after_install

there appears to be a error in the puppet changlog documentation

<https://puppet.com/docs/puppet/7/release_notes_puppet.html#new_features_puppet_7-0-0-pup-10627>

suggests

To relax permissions on the last run summary, set the group permission on the file in puppet.conf to the following: lastrunsummary = $publicdir/last_run_summary.yaml { owner = root, group = monitoring, mode = 0640 }

except

lastrunsummary

is not a valid config entry https://puppet.com/docs/puppet/7/configuration.html it should be

lastrunfile

and if set to lastrunfile,

monitoring

is not a valid group

Error: Could not get application-specific default settings: The :group parameter for the setting 'lastrunfile' must be either 'root' or 'service', not 'monitoring'

I think monitoring is just an example group name to show you that it doesn't have to be root

Oh weird... I guess it does have to be root or service.

and lastrunsummary doesnt even appear to be a valid config entry. from what i can see if should be lastrunfile. so that whole block of documentation appears to be incorrect in mulitple ways

Looks like it's lastrunfile and lastrunreport in puppet 7: https://puppet.com/docs/puppet/7/configuration.html#lastrunfile

I must be blind because i dont see a

lastrunsummary

anywhere in those docs

Looks like it's lastrunfile and lastrunreport in puppet 7: https://puppet.com/docs/puppet/7/configuration.html#lastrunfile

... That is confusing... The docs don't mention the point/preference of each, just that they're in different directories. And yeah, no lastrunsummary.

... That is confusing... The docs don't mention the point/preference of each, just that they're in different directories. And yeah, no lastrunsummary.

lastrunfile -> last_run_summary.yaml

Perhaps someone confused the file name with the config parameter?

Right.. the default value of

lastrunfile

is

$publicdir/last_run_summary.yaml

This message was deleted.

Can I trust de documentation on https://puppet.com/docs/pe/2021.6/code_mgr_config.html#configuring_code_manager? I configured PE step by step until "Test the control repository" and get this:

# puppet-code deploy --dry-run

2022/08/10 15:35:16 ERROR - Post "<https://v000762:8170/code-manager/v1/deploys>": dial tcp 127.0.1.1:8170: connect: connection refused

There seems nothing to run on port 8170 (tested with telnet)

This message was deleted.

does anyone know if $facts['aio_agent_version'], is the best way to check which major version the agent is? or is there a better way?

puppet-agent is a collection of the components, one from which is puppet

just clarifying.. i can't write puppet facts in anything but Ruby correct?

I think you can to do it in any language, but only non-structured facts

https://puppet.com/docs/puppet/7/external_facts.html It can be quirky if i remember correctly

Both are slightly incorrect. “Custom” facts must be in ruby, but you can make other facts in any language that can be interpreted on the system. Those are called “external” facts, and they can have structured data.

niiiiiiiice

I stand corrected

because.. Ruby and i aren't getting along right now

if you’re going to try and deploy them via plugin sync (putting them in your module) then you might run into errors if the language isn’t on that machine. this might’ve been fixed bc it was years ago, but I had a powershell fact that was trying to run on all our linux servers and failing bc it was windows only at the time

That should be fixed now…. Just make sure the

.ps1

file is not marked executable in your git repo (assuming you use git).

but also I think Facter knows about the extension and won’t try to run in on linux… maybe?