yea, having 10.x 192.168.x and 172.x all on your internal network...

it's so much fun

(my ISP throws me a 192 address, my personal internal network is a heavily subnetted 172/12 network and my work vpn throws a 10.x around things

This message was deleted.

:D

defining the

ssl_trust_store

does not seems to work either. I was wondering if it was hardcoded in the puppet code to use only http as there is only

http_proxy_host

in

puppet.conf

, where you cannot define

http

or

https

...

it very well may

our solution to that was to install stunnel and build a small local stunnel service to the https proxy

and just http_proxy via localhost

unfortunately the person who wrote it... didn't write it in a releasable way 😄

Well... That may be what I’ll have to do, thanks for your input

This message was deleted.

other than windows sucking I mean, is there a technical reason?

This message was deleted.

This message was deleted.

I've got a file resource that is dependent on an autofs resource. The autofs service is getting restarted/reloaded late in the puppet run. Can I have a dependency on a service reload or restart? Is it as something as easy as

require => Service[autofs]

or

subscribe => Service[autofs]

I've tried different variations of the metaparameters but I've been unsuccessful so far. Is it possible to do what I want?

For non-idempotent resources, such as

exec

, you want to use

subscribe

. For idempotent resources, such as

file

, you want to use

require

.

I've got a file resource that is dependent on an autofs resource. The autofs service is getting restarted/reloaded late in the puppet run. Can I have a dependency on a service reload or restart? Is it as something as easy as

require => Service[autofs]

or

subscribe => Service[autofs]

I've tried different variations of the metaparameters but I've been unsuccessful so far. Is it possible to do what I want? It's imperative that the autofs resource get created, autofs restart/reload and then the file resource because I need the autofs file system mounted (automatically of course!) before I start creating files/directories under that mount point.

Or maybe

Service[autofs_svc] ~> Autofs::Mount[/my/path] -> File[mounted_file]

This message was deleted.

Complete noob here - but the only reason why my company is letting me try Puppet is because Microsoft told them it was ok... https://docs.microsoft.com/en-us/microsoft-365/security/defender-endpoint/linux-install-with-puppet?view=o365-worldwide I made some Syntax corrections suggested by VSCode, but cannot seem to get past this when running puppet parser validate, as I don't understand what

default => $channel

is referencing

Error: Could not parse for environment production: Syntax error at 'default' (file: /etc/puppetlabs/code/environments/production/modules/install_mdatp/manifests/init.pp, line: 16, column: 9)

1st few stanzas:

class install_mdatp (
$channel = 'prod',
$distro = undef,
$version = undef,
) {
    case $::osfamily {
        'Debian' : {
        $release = $channel ? {
        'prod' => $facts['os']['distro']['codename']
        default => $channel
        }

I am marking this as a User issue, not a Microsoft issue.. Any help would be appreciated.

message has been deleted

I created a pull request to update the documentation https://github.com/MicrosoftDocs/microsoft-365-docs/pull/9561

This message was deleted.

This message was deleted.

businessparrot 🧑‍🏫Puppet Core Team is about to start up in #CFD8Z9A4T

This message was deleted.

what is your /etc/puppetlabs/puppet/puppetdb.conf on both nodes?