message has been deleted

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

CD4PE effectively takes the model of a single integration environment with other enviroments (such as production) being release branches based off it. That model does seem to work pretty well and its probably more supportable long-term

The thing

sensitive::mysecret

is just an example for accessing something in a user defined class named

sensitive

and getting its parameter

mysecret

. There is no feature in puppet that makes all secrets available in some scope. What you do is simply reference the variables that hold values, and some of them may have a

Sensitive

value.

regex within my enc will for some reason not work, and I need someone to tell me why i'm dumb

node name is tom1000, if I have 'tom1000': 'production' it works. If i have '\w{3}\d{4}': 'production' it does not

even adding '^\w{3}\d{4}' to ask it to start at the beginning of the string doesn't work

This message was deleted.

I guess. But it is Puppet's fault for not being a proper steward of the tech with its own ecosystem. Containers should have been the go to way to deploy puppet. Not some clunky OS heavy model of splattering bits and tools everywhere. I still love and use it, because the competitors have faultier models, but puppet just hasn't considered more grandiose models of moving to where the community wants to be.

Thanks for the clarification.

how do i stop puppetdb from managing my firewall? i went into manifests/init.pp and commented out line 76

$manage_firewall                         = $puppetdb::params::manage_firewall,

still getting:

This message was deleted.

From: https://github.com/puppetlabs/puppetlabs-puppetdb/blob/main/manifests/init.pp#L76

cd4pe and comply are on replicated and can deploy in customer kubernetes and I think we had expected PE to follow but to be blunt most large organisations are lacking the people and knowledge to operationally run kubernetes based applications at all. It's therefore been a huge amount of support effort compared to traditional deployments. I'm not saying Puppet doesn't have to work towards a cloud native / containerized solution but I don't think people are aware how big the gap still is, which is complicating how to find the right balance. When PDK was looking at being replaced with PCT and other components and developers wanted to make it container based it became clear very few enterprise customers would actually be able to use it.

I agree and to be honest once the new roadmap settles in I would be surprised if we didn't look that way in the near future

no, where you call the puppetdb class, or in hiera

This message was deleted.

say goodbye to al ci/cd pipelines until this gets fixed from puppet's side. :-(

fry dancing 🧑‍🏫 Bolt is about to start up in #CFD8Z9A4T

Hello, can anyone point me to docs/guide on how to configure litmus to perform pre-reqs, e.g. install the epel repo, before running the acceptance tests?

This message was deleted.

dumb question: i need to print a visually distinctive reminder in the agent's output. normally i would use ANSI colour sequences for this, but when i tried, it prints the raw string rather than the coloured message ... in the code:

notify { 'xxx-reminder' :
    message => "\033[0;1;37;41mthis is a reminder\033[0m" ,
  }

and in the agent output

Notice: \033[0;1;37;41mthis is a reminder\033[0m
Notice: /Stage[main]/Class/Notify[xxx-reminder]/message: defined 'message' as '\033[0;1;37;41mthis is a reminder\033[0m'

the

\033

is supposed to be an ESC character ... is there a way to make it include an actual ESC character in the agent's output?

dumb question: i need to print a visually distinctive reminder in the agent's output. normally i would use ANSI colour sequences for this, but when i tried, it prints the raw string rather than the coloured message ... in the code:

notify { 'xxx-reminder' :
    message => "\033[0;1;37;41mthis is a reminder\033[0m" ,
  }

and in the agent output

Notice: \033[0;1;37;41mthis is a reminder\033[0m
Notice: /Stage[main]/Class/Notify[xxx-reminder]/message: defined 'message' as '\033[0;1;37;41mthis is a reminder\033[0m'

the

\033

is supposed to be an ESC character ... is there a way to make it include an actual ESC character in the agent's output?

Rather than ASCII codes, a trick I like to use is changing the resource's `loglevel`: https://www.puppet.com/docs/puppet/7/metaparameter.html#loglevel

For example:

notify { 'reminder':
  message  => 'This is an important reminder',
  loglevel => 'warning',  # This makes the log entry for this resource yellow
}

For example:

notify { 'reminder':
  message  => 'This is an important reminder',
  loglevel => 'warning',
}

Also I've never seen ascii color codes in Puppet output before, so I don't think they're supported.