On Thu, Jun 27, 2013 at 5:54 PM, Andy Parker <[email protected]> wrote: > The reason I'm calling this out is because it might be an unexpected > requirement. We always say that a newer master can talk to an older agent, > but not that an older master can talk to a newer agent. In this case we will > really be making a change that requires that compatibility guarantee to the > full extent. The master will still accept YAML, and will work with older > agents, but it will issue deprecation warnings during those communications.
Maybe I'm missing something, but this comes as no surprise. The way to upgrade a puppet install has always been masters-first. In most upgrades I've done, failing to do so has led to failures, so this upgrade will be no different. I'm sure it's worth communicating this clearly and loudly in the release announcement, and if it's easy, providing clear error messages from a new agent talking to an old master. But fundamentally, I don't see any problem here. > This sets us up for removing YAML entirely (on the network, we are keeping > it for files) when puppet 4 comes along and sets us up for fewer security > problems around handling data from the network. Good riddance! Dustin -- You received this message because you are subscribed to the Google Groups "Puppet Developers" 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 http://groups.google.com/group/puppet-dev. For more options, visit https://groups.google.com/groups/opt_out.
