This message was deleted.
# puppet-enterprises
Slackbot
04/12/2023, 8:37 PMThis message was deleted.
b
bastelfreak
04/12/2023, 8:43 PMnot a console expert, but I dont think thats supported. rule of thumb is to only expose public data in facts because every node can access all facts from other nodes
c
csharpsteen
04/12/2023, 8:45 PMYup. "Sensitive" is a concept that exists for parameters of catalog resources and parameters of Tasks and Plans.
It's not a concept that exists in the universe inhabited by Fact data.
z
ziggy
04/12/2023, 9:11 PMYeah I know of
Sensitiveziggy
04/12/2023, 9:15 PMIs there a way then to hide or omit a specific fact? I dont even know why its a fact tbh
b
bastelfreak
04/12/2023, 9:20 PMyou can block facts in the facter config file
bastelfreak
04/12/2023, 9:20 PMand I think also in puppetdb
z
ziggy
04/12/2023, 9:23 PMziggy
04/13/2023, 4:17 PMI found an issue with this though ^ If a user invokes a puppet run manually, the fact goes away. On an automatic scheduled Puppet run, it comes back. Any idea why that may be @bastelfreak? Sorry for the ping..
b
bastelfreak
04/13/2023, 4:20 PMis that fact confined to something? puppet executed in a shell has was may env variables
bastelfreak
04/13/2023, 4:20 PMso maybe the fact depends on that?
z
ziggy
04/13/2023, 4:22 PMI dont think it's confined to anything. We dont use the fact for anything. It's just there (the ec2_userdata fact). We dont use it for anything.
b
bastelfreak
04/13/2023, 4:29 PMI suggest to check the code of the fact
bastelfreak
04/13/2023, 4:29 PMdid you add it to the blocklist?
z
ziggy
04/13/2023, 4:40 PMyeah it's in the blocklist, but it's only gone when a user invokes a puppet run. If it runs on the scheduled puppet run, it comes back
b
bastelfreak
04/13/2023, 5:14 PMmhm odd