and plenty will just stand up their own individual infra using https://forge.puppet.com/modules/puppetlabs/peadm and https://github.com/puppetlabs/puppetlabs-pecdm

and peadm does have its own docker setup https://github.com/puppetlabs/puppetlabs-peadm/blob/main/documentation/docker_examples.md I appreciate this is in the Puppet channel so PE may not be fully relevant here

and plenty will just stand up their own individual infra using https://forge.puppet.com/modules/puppetlabs/peadm and https://github.com/puppetlabs/puppetlabs-pecdm To test in an individual lab and play

For enterprise customers I know a lot have an engineering infrastructure

That's exactly what we have. And it's super-slow (in a certain sense). We need to go local.

allthethings 🧑‍🏫Puppet Forge is about to start up in #CFD8Z9A4T

We're seeing an operational load in customers using Puppet which comes down to these very things thinking about how to do processes which are so fundamental everyone is doing them but we don't have a standard view of how exactly to do them beyond basics. They would love to be told a standard least resistance path, which could then lead to more standard tools being developed to meet those approaches

anyone using PE 2019 have any insight as to why a custom task might not show up in the dropdown list when trying to assign 'tasks' permissions to a role?

access control -> user roles -> <userrole> -> permissions -> tasks + add permission 'instance' dropdown

the task IS on the server, but just not showing up in the list.... it has not yet been merged into the production environment either if that might have anything to do with it

I can also run it adhoc no problem

@Chris Lee I'm pretty sure for RBAC its only available from production

Personally, I see the PDK underrepresented in the topic of "how to do development with Puppet". It could be a tool that supports the entire workflow, naturally endorsing a single way to do Puppet. Obviously, it would use r10k and other already established tools under the hood. More than that, the general acceptance of PDK as a central tool defining a workflow seems low. All the teams that I have worked with recently, said that "[they] know it but [they] don't use it".

Personally, I see the PDK underrepresented in the topic of "how to do development with Puppet". It could be a tool that supports the entire workflow, naturally endorsing a single way to do Puppet. Obviously, it would use r10k and other already established tools under the hood. More than that, the general acceptance of PDK as a central tool defining a developer workflow seems low. All the teams that I have worked with recently, said that "[they] know it but [they] don't use it".

Personally, I see the PDK underrepresented in the topic of "how to do development with Puppet". It could be a tool that supports the entire workflow, naturally endorsing a single way to do Puppet. Obviously, it would use r10k and other already established tools under the hood. More than that, the general acceptance of PDK as a central tool defining a developer workflow seems low. All the teams that I have worked with recently said, "[they] know it but [they] don't use it".

Personally, I see the PDK underrepresented in the topic of "how to do development with Puppet". It could be a tool that supports the entire workflow, naturally endorsing a single way to do Puppet. From creating modules to deploying them. Obviously, it would use r10k and other already established tools under the hood. More than that, the general acceptance of PDK as a central tool defining a developer workflow seems low. All the teams that I have worked with recently said, "[they] know it but [they] don't use it".

Personally, I see the PDK underrepresented in the topic of "how to do development with Puppet". It could be a tool that supports the entire workflow, naturally endorsing a single way to do Puppet. From creating modules to deploying them. Obviously, it would use r10k and other already established tools under the hood. More than that, the general acceptance of PDK as a central tool defining a developer workflow seems low. All the teams that I have worked with recently said, "[they] know it but [they] don't use it". Sad story.

@David Sandilands thanks!

Hello...Getting below error while running Puppet agent -t on a wintel machine.

could not set 'file' on ensure Invalid argument @ dir_s_mkdir -- //./nul/20221100-1jvmrme.lock

any idea what this error about?

check the directory path(s)... if the full path doesnt exist, you have to create directories or Puppet cannot mange the directory/file you want... aka, all directories need to exist first, and puppet does not automatically create parent dirs

I have not installed any modules

just a fresh installation of puppet agent

and tried running puppet agent -t

and getting above errir

ah, ok

which path you want me to check..

are you running puppet agent in powershell as administrator?

from command prompt

as administrator?