On August 14, 2019 at 5:15 AM, Martin Alfke wrote:
Hi Dan,
On 14. Aug 2019, at 04:12, 'Dan White' via Puppet Users
wrote:
On Aug 13, 2019, at 9:30 PM, Garrett Honeycutt
wrote:
On 8/13/19 6:10 PM, 'Dan White' via Puppet Users wrote:
On Aug 13, 2019, at 9:04 PM, 'Dan White' via Puppet
Hi!
How are you building puppet-runtime? If you're using a recent version of
vanagon, I would expect you to have an
agent-runtime-6.4.x-201906190.debian-9-arm.settings.yaml file in addition
to the files you listed.
Otherwise, many of the settings used to build puppet-agent (like sysconfdir)
are
Hi Dan,
> On 14. Aug 2019, at 04:12, 'Dan White' via Puppet Users
> wrote:
>
>> On Aug 13, 2019, at 9:30 PM, Garrett Honeycutt
>> wrote:
>>
>>> On 8/13/19 6:10 PM, 'Dan White' via Puppet Users wrote:
>>> On Aug 13, 2019, at 9:04 PM, 'Dan White' via Puppet Users
>>>
On Wednesday, August 14, 2019 at 5:35:13 AM UTC-5, LinuxDan wrote:
>
> On August 14, 2019 at 5:15 AM, Martin Alfke > wrote:
>
> Hi Dan,
>
> On 14. Aug 2019, at 04:12, 'Dan White' via Puppet Users <
> puppet...@googlegroups.com > wrote:
>
>
> On Aug 13, 2019, at 9:30 PM, Garrett Honeycutt >
On August 14, 2019 at 9:01 AM, jcbollinger wrote:
Why would you not want to write to the data store backing your User resources?
If you cannot write, then you cannot manage resources -- neither create new
ones nor modify existing ones nor remove unwanted ones. These things are what
User
I believe I am going to abandon user resources with an ldap provider, because I
cannot get it to even attempt a connection.
I tried to create a user on the puppet server itself using "puppet apply"
The output of the run complains that
Provider ldap is not functional on this host
and
Could
