Provide better exception messages in Azure Automation
Exceptions are currently only surfaced by the exception message string. Please give us richer exception messages for Powershell-based runbooks, such as file name, line number, etc. Ideally I'd like to get a "regular" exception object back using Azure Powershell.
Trond Hindenes
shared this idea
Thank you for the feedback. The product team has noted this suggestion and will consider it if resourcing allows.
3 comments
-
Anonymous
commented
Add verbose and debugging capabilities when compiling state configuration files.
-
Jakob Nøtseth
commented
Any powershell module you use with AA that either by a bug or default shows a dialog message comes up with this error message: "Unable to find an entry point named 'GetPerAdapterInfo' in DLL 'iphlpapi.dll'." How do engineering team suggest that we go from this error message, to finding that some module has an error with app-only credentials and therefore tries to show the login form? Please improve debugging experience please!
-
Jakob Gottlieb Svendsen (MVP)
commented
any news on the review of this suggestion? It is very hard to debug errors in AA because of this. It has the same annoing issue as Orchestrator, which made it more complex to make runbooks as we always needed to send this detailed info out from the runbook outselves.