Fix several endpoints that no longer have <result> element wrapper.

Open dblessing opened this issue 11 years ago • 0 comments

There was a bug in Rundeck pre-2.4.0 that caused some v11+ endpoints to be wrapped in the <result> element. This client was coded according to that bug.

If we simply remove the expectation that the <result> element is there then we break compatibility with Rundeck pre-2.4.0. Instead, let's see if we can add the header X-Rundeck-API-XML-Response-Wrapper: true to these endpoints to force the <result> wrapper.

Related issue in Rundeck project - https://github.com/rundeck/rundeck/issues/1008

Dec 30 '14 20:12 dblessing