message has been deleted

Just a confirmation https://ondemand.questionmark.com/home/405096/cataloghttps://ondemand.questionmark.com/home/405096/catalog is the link to book an exam which is missing and 2019 is still the exam

message has been deleted

This message was deleted.

Hi, i currently try to use the puppet embedded ruby for an external ruby script with an additional gem install location. That itself would work without breaking puppet but i need that

/usr/local/bin/bundle

wrapper script that is not shipped with the puppet agent to do calls like

bundle install

and

bundle exec ./example.rb

. So the question can i do an alternative ruby call to do the bundle jobs or should i manually create that wrapper script for bundle here? Everything what i found currently always reference that bundler wrapper script that either shipped by the OS package or by the ruby gem itself to

/usr/local/bin/

Hi, i currently try to use the puppet embedded ruby for an external ruby script with an additional gem install location. That itself would work without breaking puppet but i need that

/usr/local/bin/bundle

wrapper script that is not shipped with the puppet agent to do calls like

bundle install

and

bundle exec ./example.rb

. So the question is can i do an alternative ruby call to do the bundle jobs or should i manually create that wrapper script for bundle here? Everything what i found currently always reference that bundler wrapper script that either shipped by the OS package or by the ruby gem itself to

/usr/local/bin/

Hi, i currently try to use the puppet embedded ruby for an external ruby script with an additional gem install location. That itself would work without breaking puppet but i need that

/usr/local/bin/bundle

wrapper script that is not shipped with the puppet agent to do calls like

bundle install

and

bundle exec ./example.rb

. So the question is can i do an alternative ruby call to do the bundle jobs or should i manually create that wrapper script for bundle here? Everything what i found currently always reference that bundler wrapper script under

/usr/local/bin/

that either shipped by the OS package or by the ruby gem itself.

But thanks for the input ❤️ @bastelfreak When you want i can provide a full example what i try to achive afterwards.

This following should ensure a seperated bundle space here i can run my scripts with new local Gems without updating the puppet agent ones:

file { 'Gemfile':
  user    => 'root',
  group   => 'root',
  mode    => '0400',
  content => [
    "# frozen_string_literal: true\n",
    'source "<https://rubygems.org>"',
    $ruby_gems_required.map |$value| { "gem '${value}'\n" },
  ].join("\n"),
}
~> exec { "${bundle_install_path}: bundle install":
  command => "/opt/puppetlabs/puppet/bin/bundle config set --local path 'vendor/bundle' && /opt/puppetlabs/puppet/bin/bundle install --jobs $(nproc)",
  cwd     => $bundle_install_path,
  creates => "${bundle_install_path}/vendor/bundle/",
  path    => $facts['path'],
}
-> exec { "${bundle_install_path}: bunde update":
  command => '/opt/puppetlabs/puppet/bin/bundle update --jobs $(nproc)',
  cwd     => $bundle_install_path,
  unless  => '/opt/puppetlabs/puppet/bin/bundle outdated --strict',
  path    => $facts['path'],
}

This message was deleted.

Hey fellow puppeteers. I am reaching out for some advice on managing XML files (in windows). Does anyone have any special techniques they use to add and manage values of elements and attributes to xml files natively in a puppet resource?

Sorry… just saw my question answered

This message was deleted.

There is Puppet Bolt as well but it uses SSH in the OSS version which is slow I’d say

This message was deleted.

I have an interesting problem in my cloud environment where I have to install RHEL package NSS for both x86_64 and i686. The problem that I'm running into is when I do a "package install nss.i686", yum/dnf tells me that nss.i686 conflicts with the nss.x86_64 package that's already installed. DNF is trying to install a newer nss version for i686 than is installed for the 64 bit version. Is there a way in puppet that I can query the existing version of nss.x86_64 and install the i686 version? I know that I can tell the package resource "install version XXX" but I won't always know what version of the 64 bit nss package is installed. Perhaps this isn't really a puppet issue but more of a yum/dnf issue. I need to pin the i686 version to the same version as the already-installed x86_64 version and allow for updates. Any ideas? https://gist.github.com/bschonec/eb0595b4f663a9778e454fcca5364dd7

that sounds like a broken repo to me, the two packages are typically built from the same srpm

so you can either manually specify the version of the package you want

$pam_version = "1.2.3"
package { ['pam.x86_64','pam.i686']: 
  ensure => $pam_version,
}

and then remember to check at patch time which version you want. OR you can write a fact that queries rpm for the version of pam.x86_64 and use that

package { 'pam.x86_64':
  ensure => 'present',
}
package { 'pam.i686':
  ensure => $facts['pam_version'],
}

(I'm going off memory so my syntax may not be 100%)

message has been deleted

This message was deleted.

There are Puppet/Hiera plugins that can integrate with Vault so that either the master can fetch secrets on behalf of an agent, or an agent can fetch a secret directly from Vault (which is more secure).

@csharpsteen That reminds me, I need to finish the PR: https://github.com/voxpupuli/puppet-vault_lookup/pull/65

@csharpsteen That reminds me, I need to finish this PR: https://github.com/voxpupuli/puppet-vault_lookup/pull/65

This message was deleted.

This message was deleted.

Yeah. The PDB performance dashboard is basically "what the devs thought might be important circa 2012". Operations dashboard includes everything we've learned in the decade since + also covers Puppet Server 😉

<http://Master.efkzvdxnvipepjklrporike02d.bx.internal.cloudapp.net:5432/puppetdb|Master.efkzvdxnvipepjklrporike02d.bx.internal.cloudapp.net:5432/puppetdb>

this is the address of my puppetdb.. shouldn't that port be 8080/8081? any clue on why it keeps writing it in as 5432?

that's postgresql's port

that explains that

thanks @vchepkov