@GSPatton long before PEADM existed, PE was around and people had a need to automate it. None of the PE environments I saw in the past years had a manual configuration. People want to automate Puppet Enterprise with Puppet. This is usually done via three modules:

Until a few months ago, none of those modules were officially supported by Puppet. The node_manager module was adopted by the content team, which is a great step forwards. All of those modules were also recommended by various PSEs at Puppet (the rbac module is even written by them).

While a task for LDAP configuration in PEADM is okay for the initial provisioning for PEADM, it solves only half of the problems. As mentioned above, people want to continuously enforce their configuration with Puppet. That doesn't work with a task, only with Puppet Code. And because Puppet ignored that in the past years, the community came up with https://github.com/abuxton/puppet_ds. I would highly appreciate it if Puppet would invest into that module and use it in PEADM instead of having a separate task in PEADM.

How many customers, roughly, use https://github.com/abuxton/puppet_ds?

This is hard to measure. The majorities of customers I interact with have a short contract for a day or week. Just to assist with their PE upgrade or a specific module development or performance problems or similar stuff. But I can say that I'm active in the Puppet ecosystem since years and I haven't seen a single PE install that, if LDAP is used, didn't rely on https://github.com/abuxton/puppet_ds. This makes is easy for customers to enforce and change LDAP settings.

pe_ldap_config task is incompatible with PE2023.8.0 #498

Description

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions