https://www.puppet.com/community logo
Join Slack
Powered by
# puppet
  • m
    @greeno We have a PR #216 to fix a RHEL versioning issue where some versions have a nn:. Please review and merge when you get moment. Thank you very much.
  • r
    message has been deleted
  • s
    This message was deleted.
    t
    n
    +3
    • 6
    • 17
  • v
    try
    Copy code
    class::param: "%{hiera('other_class::other_param')}"
  • r
    I'd be curious about the errors you're seeing. Have seen large, 100-200 internal module systems, go from 4->5 without too much trouble. I suspect you're running into internal types that have moved out of core and into modules. Example 
    cronjob
    Fairly easy fix.
  • d
    allthethings šŸ§‘ā€šŸ« Bolt is about to start up in #CFD8Z9A4T
  • s
    This message was deleted.
    s
    r
    • 3
    • 38
  • d
    kermit typing _šŸ¦ŠVox Pupuli monthly sync; see calendar event for info_ is about to start up in #CFD8Z9A4T
  • b
    I've been trying for about an hour now. Is there a way to use the fqdn_rand() function in a Hiera file? I need to run a cron job fqdn-randomly but I can't figure out the correct syntax. Something like this: (which I know is incorrect syntax): cron:hour "%fqdn_rand(59, $hostname)"
  • b
    I've been trying for about an hour now. Is there a way to use the fqdn_rand() function in a Hiera file? I need to run a cron job fqdn-randomly but I can't figure out the correct syntax. Something like this: (which I know is incorrect syntax): cron:hour "%fqdn_rand(59, $hostname)"
  • v
    you would have to write a hiera backend to understand that function
  • v
    why not do it in the class instead?
  • s
    This message was deleted.
    n
    b
    h
    • 4
    • 4
  • b
    The AIDE module accepts the minute/hour for a cron job that runs. I'd like to just specify "random hour" in the aide::hour parameter, therefore not needing to modify any code. I'm using roles/profiles methodology so I could do the randomization there but I thought it would be cleanest if hiera would accept the fqdn_rand() function.
  • s
    This message was deleted.
    r
    j
    • 3
    • 4
  • s
    This message was deleted.
    n
    • 2
    • 1
  • s
    This message was deleted.
    y
    n
    +2
    • 5
    • 15
  • n
    by serving as a variable lookup mechanism. https://github.com/ribbybibby/terraform-provider-hiera
  • s
    My conf is basically all in my `manifests/site.pp`:
    Copy code
    Apache::Vhost {
  port                         => 443,
  manage_docroot               => false,
  ssl                          => true,
  mdomain                      => true,
  use_servername_for_filenames => true,
  use_port_for_filenames       => true,
  userdir                      => 'disabled',
}
  • s
    Nice cool! If you have some "advanced" or "non default" things I would be happy you share: a lot of settings where only here in case somebody else implement the ACME protocol but back at that time there was no other options than letsencrypt which is the default one šŸ˜‰
  • s
    Ughā€¦ Noā€¦ and PHP-like error reporting that is totaly uselessā€¦ (
    unknown(line 0)
    )
  • s
    Hehe, AFK too time to go to $WORK
  • j
    I have a 
    file
    resource (e.g. 
    file { '/etc/haproxy-files/':
    ) that is recursively copying over several files. Iā€™d like to restart a service if one of those files changes (e.g. 
    /etc/haproxy-files/allowed_list
    ). Because the 
    file
    resource is recursive I canā€™t reference it like I normally would if it were an individual file (e.g. 
    File["/etc/haproxy-files/allowed_list"] ~> Service["haproxy-blah"]
    ). Any ideas for how I would go about this? Thanks!
  • n
    If just one specific of those files change, or if any of those recursive files change?
  • n
    If just one specific of those files change, or if any of those recursive files change?
  • j
    just the one file @natemccurdy
  • n
    Your best best is to make a new 
    file
    resource just for that one file, then setup your relationships with that.
  • n
    Copy code
    file { '/etc/big_dir':
  ensure  => directory,
  source  => 'puppet:///modules/foo/big_dir',
  recurse => true,
}

file { '/etc/big_dir/specific.txt':
  ensure => file,
  source => 'puppet:///modules/foo/big_dir/specific.txt',
  notify => Service['some-service'],
}
  • n
    Copy code
    file { '/etc/big_dir':
  ensure  => directory,
  source  => 'puppet:///modules/foo/big_dir',
  recurse => true,
}

file { '/etc/big_dir/specific.txt':
  ensure => file,
  source => 'puppet:///modules/foo/big_dir/specific.txt',
  notify => Service['some-service'],
}
  • j
    yea, i was thinking of making an explicit 
    file
    resource for the 
    allowed_list
    despite the redundancy
1...939495...428Latest