Puppet users - Nov 2014 - Strict ordering of structured facts in mcollective facts.yaml

After updating to facter 2.3 the structured fact ordering is different on 
every puppet run causing changes on every run.

Debug: 
/Stage[main]/Mcollective::Facts/File[/etc/mcollective/facts.yaml]/content:
--- /etc/mcollective/facts.yaml 2014-11-11 10:46:13.168223932 -0500
+++ /tmp/puppet-file20141111-10464-1y5h2e5-0    2014-11-11 
10:52:36.000000000 -0500
@@ -67,15 +67,15 @@
       minor: "5"
       full: "6.5"
     family: RedHat
-    name: CentOS
     lsb:
       distdescription: "CentOS release 6.5 (Final)"
       majdistrelease: "6"
       release: 
":base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarch"
       distrelease: "6.5"
-      distid: CentOS
       distcodename: Final
+      distid: CentOS
       minordistrelease: "5"
+    name: CentOS
   osfamily: RedHat
   other_espn_cluster_nodes: []
   partitions:

Does the community have a recommended solution for making sure the order of 
elements in structured facts are always the same when writing them to 
mcollective facts.yaml?

-- 
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/7ee21f98-0ddc-4019-9944-3227ae0d3586%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.