it looks like

gem install puppet-strings

was all i needed ... it also brought in a

puppet

gem which is newer (8.10.0) than what

brew install puppet-agent

installed (7.34.0) ... which is probably a good thing, since it's closer to what's on the servers this will be managing (8.14.0)

I highly recommend to not run

gem

as a normal user because it will puke into your home dir

and that wont help you with any of the rake tasks that people usually use

pdk bundle exec rake -T

gave me a list of something, but i have no idea what i'm looking at.

also that puppet gem you installed is dead and doesn't receive updates anymore, and the same is probably true for puppet-strings

"puppet strings" is dead?

counter question: what makes you think that perforce maintains it, when they stopped working on their modules, puppet, facter, pdk, bolt?

i wasn't aware that they had stopped working on PDK. they're still providing documentation for it, on their own web site. https://help.puppet.com/core/current/Content/PuppetCore/puppet_strings_install.htm

so funny story

as for running

gem

as a normal user ... this is part of setting up PDK on my workstation, not on a server. it pretty much has to be run as my non-root user, because i specifically don't want it touching anything that was installed as part of the ruby installed with macOS

pdk writes into your module dir, not your home dir

when they changed the license last year, they announced pdk will stay open source, without an EULA

turns out that was a lie

so are there plans for somebody to fork the last real "open source" version of PDK and move forward with it, like what openvox did to the old open source puppet? if so i'll probably give it a try, but for now we have a commercial support contract for PE which i'm assuming includes PDK, so when/if i have problems that people here can't answer, i can always open a support ticket about it (and wait several hours for a response, which is a huge part of why i'm in the slack, because people here tend to answer a bit more quickly, yourself included) (and if i haven't said it lately, thank you for that)

we're working on a toolset. pdk does two things. It can generate you boilerplate code, and it can run tests. vox pupuli already has modulesync to roll out configs for doing static code validation, unit- & acceptance testing and releasing

you can join #sig-devkit in the vox pupuli slack or on IRC

i just joined

#sig-devkit

but i'm not sure if i'll get anything out of it, at least not right away ... i'm using puppet enterprise for

#DAYJOB

, and at the moment i have another project for my personal time

@jms1: Just to clarify, PDK is still available, but the code for the tool is not publicly available anymore. The last open source version is 3.4.0, but the latest version for PDK (3.5.0) was released under the User/Developer EULA (or customer license, as all customer's are licensed to use PDK). As you have a commercial contract, PDK is automatically licensed there. If you were to be working outside a commercial contract, then you would want to sign the Puppet Core Developer EULA on your account and then you can still download PDK for free. PDK is still actively maintained and supported by Perforce Puppet. You can still use PDK in the latest versions and Perforce will continue to support it, just in a different way. Similarly for puppet-strings, I was under the impression that was still a supported module, but I'll have to go check with the team to make sure. Some portions of Puppet Core and Puppet Enterprise may no longer be open source but that does not mean they are no longer supported or developed by the team. Depending on your use case (personal use or day job) you might have a different flow to get what you need, but the functionality will be there.

so just to clarify ... as a customer, i'm allowed to download and use PDK, but i'm not allowed to see the source code for it.

Not sure which channel is best to ask, but has anyone found a “simple” way to manage /etc/krb5.conf on a linux system? It’s an ini-style file, but I don’t think the ini-file module will work very well. I just want to insert a key/value within a realm’s definition:

Hi #C0W298S9G #C19V5U41Z I have an issue setting up an ACL using posix_acl module from the forge, basically fails with the Unit Test Process with the following error, is a dependency cycle but the require is needed with default parameters is expected to compile into a catalogue without dependency cycles Any hints or clues? Thanks in advance.

# Class Code

  file { "${class::directory}/file.pem":
    ensure  => 'file',
    owner   => 'user',
    group   => 'user',
    mode    => '0440',
  }


  posix_acl { "${class::directory/file.pem":
    action      => 'set',
    permissions => [
      'default:user::r--',
      'default:group::r--',
      'default:other::---',
      'mask::r--',
      'user:user:r--',
    ],
    provider    => posixacl,
    require     => File[${class::directory/file.pem"]:
  }


# Unit Test Code

# Test file
        it do
          is_expected.to contain_file('/directory/file.pem').with(
            'ensure'  => 'file',
            'owner'   => 'user',
            'group'   => 'user',
            'mode'    => '0440',
          )
        end

        # Test POSIX ACL file
        it do
          is_expected.to contain_posix_acl('/directory/file.pem').with(
            'action'      => 'set',
            'permissions' => [
                'default:user::r--',
                'default:group::r--',
                'default:other::---',
                'mask::r--',
                'user:user:r--',
            ],
            'provider'    => 'posixacl',
           require     => File[${directory/file.pem"]:
          )
        end
      end

Why did Perforce decide to paywall the tool that encourages people to contribute code for free to the Puppet ecosystem? I'm having trouble understanding that one.

¯\_(ツ)_/¯

also vrsion 3.4 contains GPL code, I doubt that was removed in newer versions

Well it wasn't an entirely fair question because it's rhetorical and the answer is obvious: they want to make more money off of Puppet so they decided to force open source customers to pay.

New versions of PDK are no longer open source, but they do not require any payment and it is still free. We published an FAQ that answers that specific question here: https://www.puppet.com/blog/puppet-module-developer-eula-faq#can-anyone-access-the-PDK-or-is-it-only-paid-Puppet-Core-users-now

Does using it count towards the number of "nodes" governed by the license?

I don't believe so?

Sorry, I'm trying to remember the wording around nodes right now and from what I recall the nodes limit are supposed to be instances that are managed, and PDK software in and of itself shouldn't be, from my understanding.

Thanks for clarifying.