package_check_installmethod in the technique editor, but I am pretty sure that it is based on our old package lib which is not super reliable and will soon be deprecated.
ruleto apply the configuration to this group. The drawback is that the groups are based on the inventories which is only run one time per day. So this will induce a potential initial delay in your config deployment if you do not force an inventory after the installation of this pakcage.
I see. Is it possible to use a property from my node as a condition to deploy or not the file ? The idea is to configure all my snmpd's conf. So create a dédicated rule for each type of server seem pretty overkill and a pain to maintain.
So far the package_check_install works like a charm except the error if the package is not present. Note that it does what I want but the dashboard is not clean XD.
condition_from_variable_*methods. They are a bit tricky but they are well documented.
I'm not sure if this is the right place to ask, but as of today I found that there seems to be an issue with the SLES15 repository for installing the rudder agent. When trying to install I get this error message:
Retrieving repository 'Rudder' metadata ...................................................................[error]
Repository 'Rudder' is invalid.
[Rudder|http://repository.rudder.io/rpm/latest/SLES_15/] Valid metadata not found at specified URL
It looks like the primary.xml.gz was replaced with c558b0dc22b12134408b6e1baf7e2c369b45c3dd23e1247fe4c533a11467e4e0-primary.xml.gz.
Can this please be fixed?
Hello @ncharles ,
Thanks for your feedback.
Currently, I am trying to verify that our rsyslog server is configured correctly in our clients' /etc/rsyslog.conf file. So I need to make sure that the @ syslog.xxxxxx.xxx: 514 string is present in the file.
I tried using the augeas method but whether the string is present or not, it shows me "Compliant".