Cloudstack API documentation is woefully out of date #11860
Replies: 2 comments 5 replies
-
|
@ilsaloving-gander it would help if you can elaborate and pin point your issue. CloudStack API documentation is auto generated based on annotations in the java code |
Beta Was this translation helpful? Give feedback.
-
|
The ListTrafficTypes response structure is completely wrong. I haven't gone through the rest of the api but seeing how this function is so completely wrong, it makes me think something is wrong with the documentation creation. I checked the java file and it seems like it should be generating fine, but I haven't done java dev in many years so I may be wrong. I tried to create the docs myself using the wiki instructions (using mvn -Pdeveloper -Dnoredist -DskipTests clean install) , but all I get is endless compilation errors, so I question whether the documentation is even being generated correctly. So far:
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
problem
I was having trouble getting the cloudstack terraform provider to work, and I ended up tracking the problem all the way back to the API. Are the API docs edited by hand? Because they are very out of date compared to the actual API code.
This has caused a cascading set of problems with everything depending on the API, including the Cloudstack terraform provider, and the Cloudstack go library that that provider depends on.
versions
4.21
The steps to reproduce the bug
n/a
What to do about it?
Where can we find up to date documentation?
Beta Was this translation helpful? Give feedback.
All reactions