touch the file maybe? (with correct permissions)

I know I had the problem in the past, but I'm not really sure how we fixed it. I think we just truncated the file

yeah, i vaguely remember dealing with this at some point in the past decade

also if you're on puppetserver 6 or newer, you can enable the infra_inventory.txt and then agent's should only download that, not the whole file

oh cool, i’ll look into that

also, looks like moving it out of the way and touching with the correct perms worked

How can I use the urlescape puppetlabs/stdlib function in an epp template?

$idp = urlescape($whitelists['InCommon'][$whitelist])

This is what I'm trying, but it says there is no such function urlescape.

See the

puppetlabs-stdlib

module at https://forge.puppet.com/puppetlabs/stdlib?src=slack&channel=puppet

looks like maybe it's uriescape, not urlescape. Never mind.

uriescape doesn't do what I expect. Am I using it wrong? $v = uriescape('https://website.com/path/with/slashes") I expect $v to have the path with the slashes replaced with %2F, but instead I get the same thing back.

`/`’s don’t need to be uriescaped since they’re valid characters for a URI.

Why do you need to convert those to

%2F

?

`/`’s don’t need to be uriescaped since they’re valid characters for a URI.

<https://mdq.incommon.org/entities/https://idp.login.iu.edu/idp/shibboleth>

The above URL is wrong. The below one is correct.

<https://mdq.incommon.org/entities/https:%2F%2Fidp.login.iu.edu%2Fidp%2Fshibboleth>

But I guess you're right, slashes are valid in a URI. I'll try just replacing the slashes in the last part.

Yeah, it’s not going to be able to differentiate between an actual path delimiter and the the value of a path.

you can wrap CGI function into puppet's

irb(main):001:0> require 'cgi'
=> true
irb(main):002:0> CGI.escape('<https://mdq.incommon.org/entities/https://idp.login.iu.edu/idp/shibboleth>')
=> "https%3A%2F%2Fmdq.incommon.org%2Fentities%2Fhttps%3A%2F%2Fidp.login.iu.edu%2Fidp%2Fshibboleth"

Something like this

require 'cgi'
Puppet::Functions.create_function('urlencode') do
  dispatch :urlencode do
    param 'String', :url
  end

  def urlencode(url)
    CGI.escape(url)
  end
end

I swear

url_encode

was part of stdlib at some point, I could be wrong

This message was deleted.

Steve, that approach is considered anti-pattern in puppet. You, not something else, define desired state. so no guessing involved

if you need two packages, install two

also, puppet code is called 'manifest'

Hello, We are getting this error on all machines that update to the latest version Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Function Call, Failed to parse template **.erb: Filepath: /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/parser/templatewrapper.rb Line: 93 Detail: undefined method `create_erb' for Puppet:UtilModule (file: **, line: 8, column: 16) on node *****

Hello, We are getting this error on all machines that update to the latest version Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Function Call, Failed to parse template **.erb: Filepath: /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/parser/templatewrapper.rb Line: 93 Detail: undefined method `create_erb' for Puppet:UtilModule (file: **, line: 8, column: 16) on node *****

I've tried doing a full reinstall of the agent on one of the boxes

OH, Ubuntu 22.04.01 Jammy is the node

*****:~# puppet --version 7.19.0 puppet-agent/jammy,now 7.19.0-1jammy amd64

templatewrapper

? What’s that? Is that a custom function?

*****:~# puppet --version 7.19.0 puppet-agent/jammy,now 7.19.0-1jammy amd64