-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When a newer vSphere version is encountered, an error is thrown #4
Comments
I'm actually re-writing this library to not rely on vsphere-schema. Please test out the The usage is a bit different and the new API is not completely set in stone as I am working on the re-write in my spare time. There are several examples in the examples directory on that branch. The chain branch also caches the parsed wsdl data so the performance should be much better than the current code. |
That branch immediately fails with:
It looks like it's still requiring the "soap" module even though that module is no longer listed as a dependency. Adding a dependency on "soap" (by copy+pasting the dependency from master), I get "Cannot find module 'nodexml'". "soap-cookie" and "vsphere-schema" are similarly still required, even though they have been removed from Finally, after adding these 4 missing dependencies to my I did not see anything different in the example directory on your branch compared to |
Hmm, I see a new
...so it seems like the I see 'babel' listed as a dev dependency, but I don't see where you've committed/uploaded the transpiled source that's compatible with the normal node.js runtime. Is it published under a different module name, or in another directory? Or did you want me to perform a local checkout of your code and publish it somewhere myself? At the moment I've just updated my |
I just need to update the package with a build. I'll try to get that committed tonight |
Thanks. I've never played with babel so I don't have the first clue how to get it up and running. |
ive added a build and updated the package.json. the examples i was refering to are in /src/examples. unfortunately im running into a bug withthe build library i use |
Looks like that works. The new API isn't quite what's documented on https://github.com/bhoriuchi/vsphere-connect/wiki/API-V2 (e.g. It looks like not all of the functionality is exposed through the top-level API at the moment (e.g. the 'reload' method needs you to chain down to |
Yeah, I'm still working on the rewrite and documentation. It's a side project so it's a little more slow going. I'll keep this open till I publish a release |
I did notice that when there's an error from It looks like it's because You might want to remove the dual functionality of Promise-y methods that are sometimes passed callbacks - if anybody needs callback functionality, they can call Edit: or the error might be the other way around - the |
Yeah I like the idea of removing the dual callback promise code and just returning promises. |
These issues have been resolved in the current alpha release |
When attempting to use
vsphere-connect
against e.g. ESXi 6.5.0a, it throws an error.I would expect it to instead use the latest API version it understands (6.0) when it encounters a version which is too new.
Steps to reproduce against ESXi 6.5.0a:
Forcing the "API Version" to be '6.0' instead of assuming it can use whatever the server returns appears to work around this problem:
The problematic code appears to be in
lib/client/index.js
where it callsRetrieveServiceContent
then assumes that it can understand whatever API version the server returns in 'about.apiVersion', without checking whether this version is understood by thevsphere-schema
library.The text was updated successfully, but these errors were encountered: