https://www.puppet.com/community logo
Join Slack
Powered by
# voxpupuli
  • a
  • a
  • b
    @Alex Fisher do you have plans for a rewrite to grt prefetch working?
  • a
    I thought about it, but basically it would mean rewriting all the types to use credentials from a config file.
  • a
    Which for 90% of people would probably be fine, but there are maybe some users who are managing multiple remote grafana servers from the same Puppet run. They'd be less happy!
  • a
    Might be nice to be able to implement 
    instances
    though, so that unmanaged users could be purged etc.
  • a
    If I had the time and inclination, maybe just a companion 
    grafana_types
    module with all new types using the resource API and puppet device transport stuff.
  • a
    Things actually get complicated pretty quickly. eg. when returning users, should you ignore all non local users? There are ldap users, proxy auth users, oauth etc. etc. I've not got the time to work out or test trying to manage the parts of those that you can manage.
  • b
    yeah it is tricky
  • a
    For 100 users, the new implementation is ~100x faster in my testing.
  • a
    ie ~2 seconds and not ~200 seconds
  • a
    I don't suppose too many people want to manage 100 local users, but I could imagine wanting to manage a few, and the provider fetching the details of 100's of LDAP users individually for each local grafana_user in your catalog.
  • g
    @Alex Fisher ++ Thanks for teaching me a better way to validate yaml generated by Puppet!
  • d
    afisher +1! (Karma: 2)
  • a
    same technique works well for xml, json, toml etc. Really useful when you've created output using a complicated template.
  • g
    v3.5.0 of the Puppetboard has been released, please check it out! changes:
    • Report view improvements:
    ◦ show Logs before Events as they are more useful,
    ◦ show different, arguably more useful columns in Logs by default,
    ◦ allow showing messages in a “friendly” mode (like in Failures view),
    ◦ make Logs and Events filterable,
    ◦ don’t force column sizes for a better, automatic content layout,
    ◦ use fixed-width font where it makes more sense,
    • Fix mixed up normal and OFFLINE_MODE for Query view.
  • g
    v3.5.0 of the Puppetboard has been released, please check it out! changes:
    • Report view improvements:
    ◦ show Logs before Events as they are more useful,
    ◦ show different, arguably more useful columns in Logs by default,
    ◦ allow showing messages in a “friendly” mode (like in Failures view),
    ◦ make Logs and Events filterable,
    ◦ don’t force column sizes for a better, automatic content layout,
    ◦ use fixed-width font where it makes more sense,
    • Fix mixed up normal and OFFLINE_MODE for Query view.
  • j
    Almalinux 9 just came out of beta. I would like to have some sort of el9 acceptance testing soon. Has anyone given thought to adding centostream 9, alma9, etc. to metadata2gh ?
  • b
    not yet. but adding it to metadata2gh + alma/rocky/centosstreamo to our metadata.json + facterdb would be nice
  • v
    agreed
  • v
    I am currently poking https://github.com/voxpupuli/puppet-rsyslog/pull/201 and I am not sure why os.distro.codename does not resolve. lsb-release package is installed
  • v
  • v
  • r
    @bastelfreak could that be a caching problem? Like puppet tries to resolve before lsb-release is installed and then is cached as nil. Although lsb-release is installed early enough (although not before puppet?)
  • b
    mhm I do not think so
  • b
    facter isn't invoked before installing the lsb-release package
  • b
    and usually it doesn't cache
  • r
  • r
    It shouldn't be cached yes, because it could become available later
  • r
    And on 366 it searches for os.distro.codename. That line on nginx module it prints the correct value 🤷
1...515253...648Latest