-
Notifications
You must be signed in to change notification settings - Fork 226
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
Using query.next()
with no parameters does not work as specified
#903
Comments
query.next()
with no parameters does not work as specified
Thank you for the issue we will take a look and see if we can find an issue. |
…ters does not work as specified
fix (azure-iot-provisioning-server): #903 - Using with no parameters does not work as specified
@khendry - I got a fix for this committed to master, but I just missed the 11/2 release (1.8.7 I think). |
The associated fix is neither in the official version or @latest. Is there a release timeline? |
@erikerikson - I am checking with the release team |
This will be in the next release. I am hoping within the next 10 days. |
Provisioning service client released. |
Context
Description of the issue
I'm implementing an HTTP triggered Azure function to query my DPS for the list of enrolment group registration states using the
azure-iot-provisioning-server
module. I create the client, construct the query spec and when I trigger the query usingquery.next()
the function throws and error.When I modify the execution of the query, to use the query callback and wrap that in a promise, I can work around this issue. But the API does not seem to work as written.
Code sample exhibiting the issue
Console log of the issue
AB#8492768
The text was updated successfully, but these errors were encountered: