Getting rid of YAML?

90 views
Skip to first unread message

JonY

unread,
Feb 20, 2014, 5:41:33 PM2/20/14
to puppet...@googlegroups.com
Looks like my server updated to 3.4.2.  Since then I've started seeing these occasional messages like:

Feb 20 14:19:05 puppet-master[5626]: YAML in network requests is deprecated and will be removed in a future version. See http://links.puppetlabs.com/deprecate_yaml_on_network
Feb 20 14:19:05 puppet-master[5626]:    (at /usr/lib/ruby/site_ruby/1.8/puppet/network/http/handler.rb:304:in `decode_params')

Does this mean I'll be able to start using JSON or XML in my ENC scripts? 

jcbollinger

unread,
Feb 21, 2014, 11:10:23 AM2/21/14
to puppet...@googlegroups.com


The master is complaining about YAML in the inbound request from an agent.  You should stop seeing the message if you update the relevant agents to a sufficiently recent version.

The message is not related to ENC output, but inasmuch as JSON is very nearly a subset of YAML, you should be able to have your ENC output JSON now, provided that you don't tickle one of the few inconsistencies.  Not so much XML.


John

JonY

unread,
Feb 21, 2014, 11:19:10 AM2/21/14
to puppet...@googlegroups.com
All of my agents are running 3.4.0.  (or so they are told to). Is there some way to find out where this anomalous request is coming from? A $DEBUG setting or equivalent?

jcbollinger

unread,
Feb 24, 2014, 10:21:28 AM2/24/14
to puppet...@googlegroups.com


If the name of the agent being serviced is not already logged in the context of the message (look a few lines before), then you can probably get it to be logged by enabling debug logging in the master (--debug command-line option).


John

JonY

unread,
Feb 24, 2014, 10:23:33 AM2/24/14
to puppet...@googlegroups.com
Is this available via Passenger? IE a .conf setting? 
Reply all
Reply to author
Forward
0 new messages