https://www.puppet.com/community logo
Join Slack
Powered by
# puppet
  • v
    same deal, no need to duplicate attributes and support just a limited set of the resource's attributes
  • t
    and I would quote the keys of the 
    $engops_users[$this_user]
    hash, e.g 
    $engops_users[$this_user]['groups']
  • t
    and I would quote the keys of the 
    $engops_users[$this_user]
    hash, e.g 
    $engops_users[$this_user]["groups"]
  • t
    and I would quote the keys of the 
    $engops_users[$this_user]
    hash, e.g 
    $engops_users[$this_user]['groups']
  • t
    ok - thank you
  • y
    @dmnfortytwo does IRC & FreeBSD ring a bell to you 🤔 your nickname looks very familiar to me :-D
    🙃 1
  • s
    This message was deleted.
    s
    m
    n
    • 4
    • 20
  • j
    message has been deleted
  • u
    Hi, I'm trying to make hiera work with the mariadb module. I do have this in my manifests:
    Copy code
    include mariadb::server
    But when I put this in hiera I don't see any change:
    Copy code
    mariadb::server::manage_config_file: true
mariadb::server::purge_conf_dir: true

mariadb::server::override_options :
  'mysqld'                              :
    'bind-address'                      :
    binlog_format                       : MIXED
    innodb_buffer_pool_size             : 11G
    innodb_buffer_pool_instances        : 11
    innodb_log_file_size                : 1375M
    join_buffer_size                    : 512K
    key_buffer_size                     : 256M
    log_output
    What am I missing?
  • n
    It matters where in your Hiera hierarchy you put this data. Perhaps whatever matchers your hierarchy uses aren’t matching against the node you’re testing on?
  • u
    I can't remember how to query for a hiera key...
  • b
    puppet lookup... :)
  • n
    From your Puppet server, run: • 
    puppet lookup <key_name> --environment <env> --node <node_name> --explain
  • n
    From your Puppet server, run: • 
    puppet lookup <key_name> --environment <env> --node <node_name> --explain
  • n
  • b
    amd maybe --compile
  • u
    There is no puppet server...
  • u
    I use r10k and then puppet apply directly on this node.
  • n
    How exactly are you running 
    puppet apply
    ?
  • u
    puppet apply --verbose --environment production --noop /etc/puppetlabs/code/environments/production/manifests
  • n
    Okay, then just try that 
    puppet lookup
    command on that node and see what happens. (it looks like you have the code deployed to the default locations, so it may just work)
  • u
    Yes it looks like it's working
  • u
    That's a lot of output!
  • u
    It finds the key in the `common.yaml`:
    Copy code
    Path "/etc/puppetlabs/code/environments/production/data/common.yaml"
        Original path: "common.yaml"
        Found key: "mariadb::server::purge_conf_dir" value: true
  • l
    with --explain it will be fairly verbose about where it is looking and how it's deciding
  • u
    (yes I have put it there, and also in the role.
  • l
    so, the bottom of that yaml, I don't know if lining the colons up is legal in yaml
  • u
    What do you mean by lining the colons?
  • n
    The colons should be immediately after the key names. No spaces before the 
    :
  • l
    key_buffer_size                     : 256M
    to 
    key_buffer_size: 256M
1...373839...428Latest