Can you upgrade puppet agents before your puppet master?
I'm working in a fairly new PE environment. We're in our first 6 months of Puppet, including some architecture, setup workflow stuff and the early stages of developing code. I'm also the AWS administrator, with a sizable project looking to move into AWS with a very aggressive timeline. We're looking to rely heavily on Puppet for this environment, and because of that, there are some mismatches between the roadmap for each project. In short, we're still running PE 3.3 in production and dev, however, because we use VPCs in AWS, I'm really chomping at the bit to get my hands on Facter 2, which ships with the PE 3.7 agent. We're looking to set up a test instance to model the upgrade from 3.3 to 3.7, but in a first in-place upgrade, we saw some issues (There's a lot of changes, they're documented, we're going through it all) but in short, the Puppet team is hesitant to move too quickly to using 3.7.
So my question is, is there any precedence, or common understanding around the ability to upgrade puppet agents to a revision higher than the Puppet master? Docs seem to order things in terms of master first, but I haven't seen anything specifically pointing out that this isn't a viable option. This could also be useful information in terms of rollback of a PE upgrade, if the agent upgrades go out, but the new version master has an issue, and we have to revert to pointing at an older master.