-
Notifications
You must be signed in to change notification settings - Fork 5
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
Error: exception: Client id cannot be nil #12
Comments
@tombuildsstuff any ideas? |
Just saw this, running into same issue, tried both with -c and -client_id as per documentation. This is for sensu-go.
Checked the code for check-azurerm-core-usage.rb and found below:
So in theory -c, -client_id or --client should work, but unfortunately none of them do. Was anyone able to get this working? Thanks! |
Is there any more in the stacktrace? I don't have anything in azure to test with. |
Thanks for your response @majormoses! Providing some output below Quick script to get necessary values to run script
Verbose runWould this be the right way to produce the stack trace?
Output
Same but without verbose
Test without -tenant_idIt's actually taking the parameters as it complains with another error when "tenant" is missing, so assuming that -client_id is failing due to something else, not because it's missing or wrong. The error is quite cryptic though.
Is there any other way to debug/troubleshoot this? Thanks! |
Hmm can you try running this locally without the context of bonsai? It looks like it may possibly be an issue with how that is packaged.
|
Multiple attempts return same error.
# check-azurerm-cores-d-usage.rb -t "my_data" -c "my_data" -S "my_data" -s "my_data" -l "SoutheastAsia" -w 80 -c 90
Error: exception: Client id cannot be nil
CheckAzureRMCoresDUsage CRITICAL
Using Id's from following this instruction - https://docs.bmc.com/docs/cloudlifecyclemanagement/46/setting-up-a-tenant-id-client-id-and-client-secret-for-azure-resource-manager-provisioning-669202145.html
Any help in sorting this is appreciated.
The text was updated successfully, but these errors were encountered: