Open bastelfreak opened 5 months ago
This was originally filed in https://puppet.atlassian.net/browse/FACT-3065. We currently generate and upload facts to an internal build server. But we don't have automation for publishing those facts to facterdb. This is currently tracked in https://perforce.atlassian.net/browse/FACT-3065 and is currently on hold because some of those facts could contain sensitive data.
Hey, is there any update on this? And which facts could contain sensitive data? I would say that no core facts should do that, otherwise it's a bug and they should be reworked?
Use Case
FacterDB provides factsets for different operating systems. I was told that the facter team does a lot of testing on different platforms. I think it's way easier for the facter team to provide factsets instead of Vox Pupuli. We don't have access to some obscure operating systems.
Describe the Solution You Would Like
FacterDB updates from the facter team when new facter releases happen
Describe Alternatives You've Considered
Vox Pupuli maintains a Vagrantfile but that's hacky and limited to a subset of operating systems: https://github.com/voxpupuli/facterdb/blob/master/facts/Vagrantfile
Additional Context
This was raised multiple times in the past. Also via the old Jira. Since the jira migration and all the back and forth those tickets are basically lost.