-
Notifications
You must be signed in to change notification settings - Fork 245
ARM gems error out with uninitialized constant Azure #327
Comments
Thank you. Looking at it now. |
Looks good locally. Please ping back with your results. |
Hi @devigned thanks for the update. I pulled your latest changes and installed v.0.2.1. I'm no longer hitting the uninitialized constant error when requiring the gems. I see other errors with rspec, but I think those might be issues on my end. Thanks! Marking this as closed. |
Yeah... the project setup right now has an excepectation that you will do a We need to clean up the test / developer workflow as it's rather awkward right now. Thank you for the issue report and for the prompt response. Please don't hesitate to provide feedback. Cheers! |
Hi @devigned , just a question here about auth and service principals, only loosely related to this issue. I tried running the tests again and I get an error stating:
That make sense to me because as I understand it, the tests generate a new resource group each time. Thing is, my service principal does not have access to those groups yet. Is there a way to give my service principal access to all the resource groups in my subscription? Or at least to all the resource groups that it creates? Thanks in advance! |
Awesome question! You can give your service principal contributor rights to your subscription. In the Azure portal, click on Subscriptions, click on the user icon, then add your user or find the service principal / application and give the service principal rights to contribute to the subscription. See below. |
Ah cool, I didn't realize you could dig deeper into subscriptions via the portal. Thanks! |
The 0.2.0 versions of the Azure Resource Management gems throw an error "uninitialized constant Azure".
To repro, either
rspec
or
gem install azure_mgmt_compute:0.2.0
irb
require 'azure_mgmt_compute'
Rather than loading the required gem, I get the error that Azure is an uninitialized constant.
The text was updated successfully, but these errors were encountered: