search

azureautomation / azure-automation-ise-addon

The Azure Automation PowerShell ISE Add-On makes it easy to author and test your runbooks in your local PowerShell ISE
https://www.powershellgallery.com/packages/AzureAutomationAuthoringToolkit/
Other
122 stars 24 forks source link

Unable to pull down runbooks #156

Closed wsmelton closed 6 years ago

wsmelton commented 6 years ago

Upon login to my Azure Subscription I am getting this error from PowerShell ISE: image

It will not actually show the current runbooks I have under the Automation account. I am logging in as the subscription owner so it is not a permissions issue.

eamonoreilly commented 6 years ago

Is there any error in the status window? If you uncheck the RunAs, does it work correctly? I haven't seen this issue so I'll need to investigate some more. Is it consistent across different automation accounts? Thanks for reporting, Eamon

wsmelton commented 6 years ago

Nothing show as error in the status window: image

wsmelton commented 6 years ago

I switch to a brand new runbook that I just created and the same bad request prompt is given. I have also unchecked RunAs and the error prompt does not show up, but I'm still missing the assets under runbooks and DSC.

eamonoreilly commented 6 years ago

Can you uncheck the Run As box and then sign in again? I'm hoping that the code path that gets executed outside of the RunAs path would produce a better error? Also, an option would be to build the add on locally if you have Visual Studio installed and see what line it is failing on. I could also jump on a skype call also if neither of the above work. thanks, Eamon

wsmelton commented 6 years ago

Unchecking the runas I did previously. It does not provide any error prompt or additional info on the status box.

artisticcheese commented 6 years ago

Happening to me too.

eamonoreilly commented 6 years ago

Thanks guys. I think I have found the issue. There is a new way to add a credential to an existing AD application and the way I do it currently is no longer supported. This involves moving to a new AD client nuget package so might take me a little time and then to change the code as needed. Thanks, Eamon

eamonoreilly commented 6 years ago

I created a release to address this issue. It is available on the PowerShell Gallery If you still see the issue, please reopen. Thanks again guys for reporting. Eamon