You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In IoT docs that are designed to work with the AZ3166 DevKit, such as this one, the instructions guide users to download an install package for Windows or macOS. Where can we find the GitHub repository containing the contents of that install package?
I'd like to submit a PR against that package so that the IoT DevKit docs will work even when users only have resource group-level access in Microsoft Azure (right now they won't without modifying the downloaded package because it assumes users have rights to register resource providers in the subscription and always tries to register a resource provider rather than checking to see if the resource provider it needs is already registered first).
Thanks!
The text was updated successfully, but these errors were encountered:
@Tysonn That's the right repo, but I found out from @ArthurMa1978 that the code I was modifying was not open source (yet), and that an update was being worked on, so under his recommendation I logged an issue with the changes I had made locally here. With that logged, I'm going to close this issue.
In IoT docs that are designed to work with the AZ3166 DevKit, such as this one, the instructions guide users to download an install package for Windows or macOS. Where can we find the GitHub repository containing the contents of that install package?
I'd like to submit a PR against that package so that the IoT DevKit docs will work even when users only have resource group-level access in Microsoft Azure (right now they won't without modifying the downloaded package because it assumes users have rights to register resource providers in the subscription and always tries to register a resource provider rather than checking to see if the resource provider it needs is already registered first).
Thanks!
The text was updated successfully, but these errors were encountered: