Puppet Community

pdk usually contains 3? ruby versions for the different puppet versions. by default it uses the latest supported puppet version that your metadata.json allows

I see. Is there a way to use other than the default version?

<https://github.com/puppetlabs/pdk/issues/801#issuecomment-553222358> , maybe this helps?

Worked great for Puppet 6! Just had to downgrade one dependency in Gemfile. For older versions, it failed with `Unable to find a Puppet gem matching ~&gt; 5.0`. Does it mean there's no support in pdk? If so, trying an older version for pdk itself might work?

(Yes, I know Puppet &lt; 6 is obsolete. Just want to make sure I have some way to test current module specs.)

if it works in 6, it is likely to work in 4+

<@U020LK7D0JU> Do you mean the module, or pdk? If pdk, do you have an idea on how?

My attempt now is to run in a VM with Puppet 5

the puppet language basically didn't change all that much from 4 to 6, most of it is behind the scenes changes

OK. The Puppet 5 try miserably failed, so I'll just be happy with Puppet 6 results.

keep it simple, and then look into litmus or voxpupuli's acceptance

and do acceptance tests (which you totally can setup for older versions, because it's basically just running `puppet agent -t`

tomcat7 and tomcat8 are already didferent names

Sorry not move take a copy using cp command

Both have same directory name ie for tomact 7 path is /opt/tomcat and for tomcat 8 path is /opt/tomcat .

Because both have same path as mentioned above

I would try to build a proper rpm/debian package

Incase of anything wrong in upgrade i can revert back

$tomcat_directory = '/path/to/tomcat'
$backup_directory = '/path/to/backup'
file { $backup_directory:
  ensure =&gt; directory,
}

file { "${backup_directory}/tomcat_backup":
  ensure  =&gt; directory,
  recurse =&gt; true,
  source  =&gt; $tomcat_directory,
}

again, I recommend building a proper package

the package manager is built to handle upgrades and downgrades

there are reference docs from each operating system

an fpm is a nice generic tool for building packages for different platforms

<https://github.com/jordansissel/fpm|https://github.com/jordansissel/fpm>

I've a customer that's happy with <https://www.enterprisemodules.com/> . The developer <@U125ETYQP> is also on slack

We have a supported commercial puppet module called <https://www.enterprisemodules.com/shop/products/puppet-ora_install-module?taxon_id=14|ora_install>, that delivers the functionality to <https://www.enterprisemodules.com/docs/ora_install/opatchupgrade.html|update opatch> and a <https://www.enterprisemodules.com/docs/ora_install/ora_opatch.html|Puppet type that can patch Oracle homes>.  If you are interested I’d love to give you a small demo. Let me know if I can do anything for you.

:fry_dancing: _Content and Tooling_ is about to start up in <#CFD8Z9A4T|>

I'm very close with:

`foo:`  
  `'clear_cache':`
    `command: "epp('puppet_nfii/sssd_join.epp'), { admin_password: %{lookup('admin_password')}, admin_name: %{lookup('admin_name')} }"` 
    `timeout: 60`
    `tries: 2`
    `notify:`
      `- Exec[clear_cache]`
      `- Service[sssd]`

But I think I've just reproduced a string, not a resource.

if it 's in a module called sssd, and admin_name, admin_password, and computers_ou are parameters to sssd, then you can skip the lookup and just reference the variables

because hiera Automatic Parameter Lookup will take care of it

but I don't entirely make resources into hiera ever

I'm using sgnl05-sssd module; there aren't any admin/password parameters so I have to use lookup to populate my EPP file.

See the `sgnl05-sssd` module at <https://forge.puppet.com/sgnl05/sssd?src=slack&amp;channel=puppet>

this is exactly what profiles are for :slightly_smiling_face:

<https://www.puppet.com/docs/puppet/7/the_roles_and_profiles_method.html>

I've got hiera separated into RedHat and OraclLinux hierarchies so in my RedHat.yaml file, I wanted to create the exec resource rather than "if os = redhat then &lt;build this&gt;, else &lt;build that&gt;"

Perhaps I'm using roles and profiles wrong but I've got almost everything in hiera.

yea, you can still do that, but it will be much less complex if you can have a real exec resource and APL

profile::sssd could have all the variables you need in addition to the sssd standard ones

and then you can just have the exec using profile_sssd::admin_password etc

I'll see if I can make that happen.  Thanks for the help.

I have a strong opinion that putting resource definitions into Hiera is anti-pattern.. though I know there is a lot of ppl who uses it and they are happy with it.

Hello, everyone.  Is there puppet7 agent for RHEL 9 aarch64? Not seeing it under <https://yum.puppet.com/puppet7/el/9/index.html>.  Thank you.

This is probably a good reference of what would be available. I don’t see the aarch64 build for rhel9: <https://github.com/puppetlabs/puppet-agent/tree/main/configs/platforms> — that being said, it is totally possible that the one for rhel8 would work? (To be clear, i make no claim that it would, but it might be worth testing)

There were some recent discussion about that though (maybe in one of the other channels?)

Well, puppet is open-source, so: <https://github.com/puppetlabs/puppet-agent>, <https://github.com/puppetlabs/puppetserver>

q3 for additional el9 stuff, but I am not sure if that includes aarch64

Our whole project of upgrading to RHEL 9 is then going nowhere…. Damnit. I wish i looked into this earlier…

I ended up setting `expire_logs_days: undef`, but this parameter is deprecated so it may eventually prevent MariaDB from starting.

See the `puppetlabs-mysql` module at <https://forge.puppet.com/puppetlabs/mysql?src=slack&amp;channel=puppet>

puppet 7 aarch64 agent for RHEL 8 seems to work on RHEL 9.

fixing the comments, I can't quite tell what has the acceptance tests broken

:mailbox_with_mail: waiting for a rerun when you have a few minutes

Does anyone have a good pql to ast converter?