On 1/29/16, 11:14 AM, "Gareth Humphries" <puppet-users@googlegroups.com on behalf of gareth.humphries...@gmail.com> wrote:
Normally, yes, but in this case it needs a class list locally to populate the fact, and it doesn't have that until after a run. Facts get sent to the master, where classes are allocated and a catalog compiled, then the catalog sent back to the client. Without the initial catalog, the client has no knowledge of the classes, and can't set the fact accordingly. If I could set the fact on the server I'd be away, but I haven't yet found a way to get that working. This is proving harder than initially thought. I think I might have to shelve it. :-( I’m also having a hard time understanding the end goal. It seems like you have information based on the classes assigned to a host that determine it’s role. You want to use those classes to set a role fact on the node. What I don’t understand is that if you have a defined set of logic you can apply to determine the role, who you need a role fact at all? What in the classes is required for you to determine this? Jason -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/D3737985-FEE6-4DF2-878C-E2D94C8CE156%40tacorp.net. For more options, visit https://groups.google.com/d/optout.
