Le 09/04/2024 à 09:01:42-0700, Mike Langhorst a écrit Hi, > So, assuming that you were to export this resource on 2 different hosts. How > could you collect it <<| |>>, as there could only be one /etc/something.conf > on > that collecting host. That's why the exported resource path needs to be > unique, can't just name it something unique if the resulting file would be in > conflict.
Well...I'm not a dev maybe it's way I don't understand.... if I export to two differents host/tags those files are on two differents hosts. How can they be in conflict ? For example, if I have «something» let's say a service/daemon running on «master-host» and for each «slave-host» I need to put a config file who depend on a token distributed by the master. For me the most «natural» method would be to exported the «token» to each slave host from the master. I don't see how can that be conflict. regards -- Albert SHIH 🦫 🐸 France Heure locale/Local time: ven. 12 avril 2024 09:32:07 CEST -- 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/Zhjk_vTwGh1QTu9b%40io.chezmoi.fr.
