https://www.puppet.com/community logo
Join Slack
Powered by
# puppet
  • j
    I see we actually do too, so I guess it works too because we don’t face problems
  • j
    what is this 
    :latest
    ?
  • j
  • j
    Yeah, looks right from what you’re showing me - maybe this helps in some way? https://github.com/voxpupuli/puppet-r10k/issues/409
  • d
    waiting 🧑‍🏫 Bolt is about to start up in #CFD8Z9A4T
  • s
    This message was deleted.
    l
    w
    +4
    • 7
    • 61
  • d
    fry dancing _🦊Vox Pupuli monthly sync; see calendar event for info_ is about to start up in #CFD8Z9A4T
  • w
    What puppet release should be used for fedora 33?
  • r
    Lastly you can play some games in your cloud-init (kickstart?) phase before Puppet runs. 
    apt-get update && etc etc
    or just populating all the service accounts if you're not using ldap/sssd for that. Might help cut down on the time in Puppet.
  • c
    33 doesn’t appear to be supported yet. Only 32
  • c
    actually, I just found 34 & 36
  • c
    33 seems to not exist.
  • c
  • w
    Will try my luck with 34 than
  • h
    I think we typically ran the prior version (i.e. 32). Please keep in mind that Fedora <36 is end of life or will be shortly
    👍 1
  • s
    This message was deleted.
    n
    b
    p
    • 4
    • 11
  • n
    Is the toy-chest puppetserver image different from https://github.com/puppetlabs/puppetserver/tree/main/docker/puppetserver ?
  • s
    This message was deleted.
    t
    • 2
    • 1
  • n
    $name
  • s
    $module_name
    ?
  • s
    This message was deleted.
    👍 2
    t
    n
    • 3
    • 4
  • s
    This message was deleted.
    r
    n
    +4
    • 7
    • 27
  • n
    Do you mean literally a "noop" as in the 
    noop
    metaparameter of Puppet? Or do you mean something like Python's 
    pass
    which just evaluates to nothing and continues on? I'm gonna assume the latter because Puppet errors out on branches of an 
    if
    statement that don't evaluate to anything and I'm guessing you're hitting that error?
  • n
    Hmm... maybe that parser feature got turned off in a recent update... I can't get it to error out on an 
    if
    statement that produces no value anymore. Weird 🤷
  • n
    facts
    is a reserved word and cannot be defined in local scopes, it only ever exists in "top scope". So there will never be any ambiguity in the variable named 
    facts
  • s
    If you have te deal with arch specific things in your control-repo, you can also do this kind of things (from my control-repo where it is linux vs windows):
    Copy code
    class profile::base {
  include "profile::base::${fact('kernel')}"
  # [...]
}
  • y
    I’m fan of “lest” function these days :) writing from phone so might be not fully correctt
  • y
    I’m fan of “lest” function these days :) writing from phone so might be not fully correct
  • n
    In your case, I imagine the 
    software
    fact would be better as a JSON file. Like this:
    Copy code
    $ cat /etc/puppetlabs/facter/facts.d/software.json
{
  "software": [
    "Firefox",
    "Opera",
    "Google Chrome",
    "Nmap"
  ],
  "foo": "bar"
}
    Note that this creates two facts: • One called 
    software
    , that is an Array of Strings. • One called 
    foo
    , that is a String. Using those facts would look something like this:
    Copy code
    $ cat fact_test_json.pp
notice("foo resolves to: ${facts.get('foo')}")

# Iterate over each array item in the `software` fact, then notice() it:
$facts.get('software').each |$package_name| {
  notice($package_name)
}
    Applying that Puppet code looks like this:
    Copy code
    $ sudo puppet apply fact_test.pp
Notice: Scope(Class[main]): foo resolves to: bar
Notice: Scope(Class[main]): Firefox
Notice: Scope(Class[main]): Opera
Notice: Scope(Class[main]): Google Chrome
Notice: Scope(Class[main]): Nmap
Notice: Compiled catalog for nate.localdomain in environment production in 0.05 seconds
Notice: Applied catalog in 0.01 seconds
  • n
    In your case, I imagine the 
    software
    fact would be better as a JSON file. Like this:
    Copy code
    $ cat /etc/puppetlabs/facter/facts.d/software.json
{
  "software": [
    "Firefox",
    "Opera",
    "Google Chrome",
    "Nmap"
  ],
  "foo": "bar"
}
    Note that this creates two facts: • One called 
    software
    , that is an Array of Strings. • One called 
    foo
    , that is a String. Using those facts would look something like this:
    Copy code
    $ cat fact_test_json.pp
notice("foo resolves to: ${facts.get('foo')}")

# Iterate over each array item in the `software` fact, then notice() it:
$facts.get('software').each |$package_name| {
  notice($package_name)
}
    Applying that Puppet code looks like this:
    Copy code
    $ sudo puppet apply fact_test_json.pp
Notice: Scope(Class[main]): foo resolves to: bar
Notice: Scope(Class[main]): Firefox
Notice: Scope(Class[main]): Opera
Notice: Scope(Class[main]): Google Chrome
Notice: Scope(Class[main]): Nmap
Notice: Compiled catalog for nate.localdomain in environment production in 0.05 seconds
Notice: Applied catalog in 0.01 seconds
1...252253254...428Latest