You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently I observe that a lot of facts/factsets pushed in puppetdb which is not needed. For example I don't need info about virtual interfaces on host, like cali, docker, veth and etc. Currently I can block only all interfaces in blocklist like "networking.interfaces" but not "networking.interfaces.cali.*", "networking.interfaces.veth.*", "networking.interfaces.docker.*", "networking.interfaces.macvtap.*", "networking.interfaces.vnet.*", "networking.interfaces.tunl.*".
Also it's impossible to block on puppetdb level because of new structure with hashes instead of flat sctructure.
Also block doesn't work for 3rd level of hierarchy like "networking.interfaces.docker0" doesn't block this fact, only whole "networking.interfaces" works.
Describe the Solution You Would Like
I would like to store less facts in puppetdb and/or output in facter output. It would be perfect if we can block facts/facts block by wildcard/regexp (like in puppetdb with facts-blocklist-type = regex).
The text was updated successfully, but these errors were encountered:
@sharewax we have an issue filed to allow portions of structured fact values to be filtered in #2658 I think that would solve your use case.
it's impossible to block on puppetdb level because of new structure with hashes instead of flat sctructure.
This sounds like a bug in puppetdb. I would expect it's possible to block structured facts to limit the amount of data stored there, especially since legacy facts are disabled by default in Puppet 8. Maybe the facts-blocklist-type setting has never worked with structured facts?
Based on that I'm thinking we should close this as a dup of 2658 and file a separate issue for puppetdb. Thoughts?
Use Case
Currently I observe that a lot of facts/factsets pushed in puppetdb which is not needed. For example I don't need info about virtual interfaces on host, like cali, docker, veth and etc. Currently I can block only all interfaces in blocklist like "networking.interfaces" but not
"networking.interfaces.cali.*", "networking.interfaces.veth.*", "networking.interfaces.docker.*", "networking.interfaces.macvtap.*", "networking.interfaces.vnet.*", "networking.interfaces.tunl.*"
.Also it's impossible to block on puppetdb level because of new structure with hashes instead of flat sctructure.
Also block doesn't work for 3rd level of hierarchy like
"networking.interfaces.docker0"
doesn't block this fact, only whole"networking.interfaces"
works.Describe the Solution You Would Like
I would like to store less facts in puppetdb and/or output in facter output. It would be perfect if we can block facts/facts block by wildcard/regexp (like in puppetdb with facts-blocklist-type = regex).
The text was updated successfully, but these errors were encountered: