dsccommunity
Exception handeling hides errors, makes troubleshooting more difficult
I had an issue using this resource over the last week to import a bacpac. The issue turned out to be with my SQL Server and not with the resource, however, with the way error are simplified to a single line instead of re-throwing the original exception, debugging the issue took longer than it should have.
Is there a specific reason that all of the exceptions are hidden? Could there be a middle ground for passing the original exception, maybe write-debug?
We should aim to display as much information as possible (as long as it's potentially useful to identify the root cause of an issue), if you see some error handling code which hides information useful for debugging, please file a specific bug or feel free to send PR - we will gladly accept those contributions :)
