Would it be possible to have the distributed config.yaml file for razor-server set the protect_new_nodes value to true instead of false?
I ask because it appears the latest update moved my config.yaml to config.yaml.rpmsave and replaced it. We have a very established base, and a developer just today rebooted his system and it was one razor had never seen. It got wiped and reinstalled because of the config change. Perhaps I should have noticed it before today, but I didn't. I didn't expect an upgrade to reset my preference on this value. Setting this to "true" might inconvenience those who want it "false", but the reverse is destructive and might be unrecoverable. Say what you want about backups and keeping code in repositories, but when a simple reboot leads to an unexpected system reinstallation, that's not good. Thanks, Bret -- You received this message because you are subscribed to the Google Groups "puppet-razor" 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/puppet-razor. For more options, visit https://groups.google.com/d/optout.
