Oh, I see the key changed from 'global' to 'nagios-env'. Were the docs just wrong and it was escaping detection previously or did this backwards-incompatible change get purposely made in a point release?
Greg From: Greg <[email protected]<mailto:[email protected]>> Reply-To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Date: Friday, July 18, 2014 1:43 PM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: new error I was revisiting my Ambari API testing with the most recent changes and the code that worked a few weeks ago no longer is. Apparently the way that is shown in the docs to define the nagios_contact no longer works. I sent this in my blueprint: "configurations": [ { "global" : { "nagios_contact" : "[email protected]<mailto:[email protected]>" } } ], But when I attempt to create that blueprint, I get a 400 error with the following message: Required configurations are missing from the specified host groups: {gateway={nagios-env=[nagios_contact]}} ('gateway' is the name of one of my host_groups). This error did not occur as of the latest code 3-4 weeks ago. What do I need to be doing differently? Greg
