I'm not sure if this is an issue in the Chef API, as it behaves the same way since Chef 10. Perhaps this has gone unnoticed since then, but given that the API behavior has not changed I tend to think this is an issue in our side. If we had built the API by looking at the real responses instead of taking the docs as an example, this issue should have not appeared.
Anyway, let's see what Chef ninjas have to say in the thread @noorul has opened in the ML and then document this accordingly. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-chef/pull/30#issuecomment-25698855
