On 23/02/17 10:42, Marc Haber wrote: > I then, as usual, create an Environment branch01a in foreman and let > it import the classes by clicking in the environment list on the arrow > next to "Classes" and selecting "Import from" in the drop-down. > Foreman works a bit, reports a green window, but the class list > imported is an obsolete one. Classes deleted in branch01a still show > up in the class list, and the new classes defined in branch01a dont > show. > > Do I see correctly that Foreman does not look into the local file > system but does instead query the puppet server for a list of its > environment?
The behaviour depends on the Puppet version being used and as configured in the smart proxy's puppet.yml configuration file. On Puppet 3.x without directory environments, the module path is determined from puppet.conf and the manifests parsed by the smart proxy. This may be cached inside the smart proxy based on the mtime of the files if :use_cache is enabled. On 3.5-3.8 with directory environments, the module path is determined by querying the Puppet master or server, and manifests parsed as above. On 4.x, the Puppet Server resource_types or environment_classes APIs is queried returning the parsed data. The server may be configured to cache manifests. -- Dominic Cleal [email protected] -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
